Proj davinci dev #9
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…webview#1037) * Fix Android build errors when using Gradle 6.0 * Update gradle.properties * Remove newline at end of file * newline
## [7.5.2](react-native-webview/react-native-webview@v7.5.1...v7.5.2) (2019-11-26) ### Bug Fixes * **android:** Added fallback poster image to prevent crashes ([react-native-webview#1036](react-native-webview#1036)) ([d8acd90](react-native-webview@d8acd90)) * **build:** Android build errors when using Gradle 6.0 ([react-native-webview#1037](react-native-webview#1037)) ([5b0c634](react-native-webview@5b0c634))
…ve-webview#1038) * Run the injectedJavaScript on DocumentStart for iOS * Add new prop injectedJavaScriptBeforeContentLoaded Update types Update docs * Self review
# [7.6.0](react-native-webview/react-native-webview@v7.5.2...v7.6.0) (2019-12-06) ### Bug Fixes * **ios:** Make allowFileAccessFromFileURLs work in iOS. ([react-native-webview#1061](react-native-webview#1061)) ([88b6498](react-native-webview@88b6498)) ### Features * **iOS:** new prop injectedJavaScriptBeforeContentLoaded ([react-native-webview#1038](react-native-webview#1038)) ([604495e](react-native-webview@604495e))
) BREAKING CHANGE: if you use onNavigationStateChange on iOS it will now trigger on # changes to the url. * Hook the `window.history` API on iOS to generate events The underlying WKWebView doesn't seem to generate any events in response to the `window.history` API - none of the `WKNavigationDelegate` methods fire. Given this limitation, the only way to know when the location changes via this API is to inject Javascript into the page and have it notify the native code directly when any of these functions are called. The `setTimeout` call gives up the current tick, allowing the location to change before firing the event. * Remove the outdated section about hash changes Now that this bug is fixed, the workaround is no longer required.
# [8.0.0](react-native-webview/react-native-webview@v7.6.0...v8.0.0) (2019-12-16) ### Features * **ios:** Generate history API events on iOS ([react-native-webview#1082](react-native-webview#1082)) ([3615296](react-native-webview@3615296)) ### BREAKING CHANGES * **ios:** if you use onNavigationStateChange on iOS it will now trigger on # changes to the url. * Hook the `window.history` API on iOS to generate events The underlying WKWebView doesn't seem to generate any events in response to the `window.history` API - none of the `WKNavigationDelegate` methods fire. Given this limitation, the only way to know when the location changes via this API is to inject Javascript into the page and have it notify the native code directly when any of these functions are called. The `setTimeout` call gives up the current tick, allowing the location to change before firing the event. * Remove the outdated section about hash changes Now that this bug is fixed, the workaround is no longer required.
## [8.0.1](react-native-webview/react-native-webview@v8.0.0...v8.0.1) (2019-12-17) ### Bug Fixes * **iOS:** Ignore WebKitDomainError 101 ([react-native-webview#961](react-native-webview#961)) ([adb5608](react-native-webview@adb5608))
## [8.0.2](react-native-webview/react-native-webview@v8.0.1...v8.0.2) (2019-12-27) ### Bug Fixes * **iOS:** WKWebView RetainCycle ([react-native-webview#1096](react-native-webview#1096)) ([4f4644f](react-native-webview@4f4644f))
Bumps [npm](https://github.com/npm/cli) from 6.11.3 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](npm/cli@v6.11.3...v6.13.4) Signed-off-by: dependabot[bot] <[email protected]>
* docs: add Lean core badge * docs: adjust badge style
* Preventing an unhandled promise rejection when: a URL is loaded by the WebView, but the URL isn't in the origin whitelist, so it is handed off to the OS to handle by calling Linking.openURL(), but Linking.openURL has an error. The code wasn't catching the error, so this would result in an unhandled promise rejection. Now the error is being caught. * Fixing a problem where a URL is handled to the OS to deal with, via Linking.openURL, and also loaded in the WebView by making those cases mutually exclusive (they weren't previously). In more detail: when a URL is loaded by the WebView that isn't in the origin whitelist it is handled off to the OS to handle by calling Linking.openURL. But, if the onShouldStartLoadWithRequest prop is set, then that function would also be called, and then that would determine whether the URL should be loaded. This can result in a situation where the URL is passed to Linking.openURL and onShouldStartLoadWithRequest returns true so it is also loaded in the WebView. The client can fix this by duplicating the origin whitelist logic in their onShouldStartLoadWithRequest of course, but this change makes it so they don't have to. Co-authored-by: Jason Safaiyeh <[email protected]>
## [8.0.3](react-native-webview/react-native-webview@v8.0.2...v8.0.3) (2020-01-08) ### Bug Fixes * **whitelisted origins:** Prevent handling of un-whitelisted URLs ([0442126](react-native-webview@0442126))
…onflict warning This converter is already defined in [RCTScrollViewManager.m](https://github.com/facebook/react-native/blob/master/React/Views/ScrollView/RCTScrollViewManager.m#L40). Redefining it in react-native-webview can cause undefined behaviour when used. Since ScrollView is unlikely to go away, we can take a dependency on it. All current tests should pass. When building a React Native app with `react-native-webview`, the following warning can be seen in the build logs: ``` Meta method 'UIScrollViewContentInsetAdjustmentBehavior:' in category from /~/Library/Developer/Xcode/DerivedData/App-geojljebaazfrrgvxfkjjpiwmdlg/Build/Products/Debug-iphonesimulator/React-Core/libReact-Core.a(RCTScrollViewManager.o) conflicts with same method from another category ``` The warning should go away after removing the offending function. Co-authored-by: Jason Safaiyeh <[email protected]>
## [8.0.4](react-native-webview/react-native-webview@v8.0.3...v8.0.4) (2020-01-20) ### Bug Fixes * **iOS:** Meta method 'UIScrollViewContentInsetAdjustmentBehavior:' conflict warning ([e6edc6d](react-native-webview@e6edc6d)), closes [/github.com/facebook/react-native/blob/master/React/Views/ScrollView/RCTScrollViewManager.m#L40](https://github.com//github.com/facebook/react-native/blob/master/React/Views/ScrollView/RCTScrollViewManager.m/issues/L40)
…ebview#991) Co-authored-by: Jamon Holmgren <[email protected]> Co-authored-by: Jason Safaiyeh <[email protected]>
## [8.0.5](react-native-webview/react-native-webview@v8.0.4...v8.0.5) (2020-01-26) ### Bug Fixes * **Android:** Redirected URLs now redirect correctly. ([react-native-webview#991](react-native-webview#991)) ([acf1ad7](react-native-webview@acf1ad7))
## [8.0.6](react-native-webview/react-native-webview@v8.0.5...v8.0.6) (2020-01-30) ### Bug Fixes * **Android:** Revert "Redirected URLs now redirect correctly. ([react-native-webview#991](react-native-webview#991))" ([react-native-webview#1177](react-native-webview#1177)) ([344aab5](react-native-webview@344aab5))
# [8.1.0](react-native-webview/react-native-webview@v8.0.6...v8.1.0) (2020-02-12) ### Features * **macOS:** macOS Support ([react-native-webview#1164](react-native-webview#1164)) ([1e57231](react-native-webview@1e57231))
…view#1194) * RN is implementation dependency * renamed: RNCWebViewPackage.java -> RNCWebViewPackage.kt * migrate RNCWebViewPackage to Kotlin Co-authored-by: Jason Safaiyeh <[email protected]>
…ive-webview#1657) Co-authored-by: Thibault Malbranche <[email protected]>
…native-webview#1077) * fix:iOS13 scrollView.automaticallyAdjustsScrollIndicatorInsets default value YES which make the webview vertical indicator position in wrong offset * added types and doc Co-authored-by: BillHsieh <[email protected]> Co-authored-by: xietian <[email protected]> Co-authored-by: Thibault Malbranche <[email protected]> Co-authored-by: Thibault Malbranche <[email protected]>
# [11.1.0](react-native-webview/react-native-webview@v11.0.3...v11.1.0) (2021-01-20) ### Features * **iOS 13+:** automaticallyAdjustsScrollIndicatorInsets prop ([react-native-webview#1077](react-native-webview#1077)) ([d46a6d3](react-native-webview@d46a6d3))
…tive-webview#1730) * Added allowUniversalAccessFromFileURLs property to iOS and macOS Updated the types to include allowUniversalAccessFromFileURLs and allowFileAccessFromFileURLs for iOS and macOS Updated the Reference.md to include in the allowUniversalAccessFromFileURLs section iOS and macOS * Updated platform in the type definition
# [11.2.0](react-native-webview/react-native-webview@v11.1.0...v11.2.0) (2021-01-20) ### Features * **iOS & MacOS:** allowUniversalAccessFromFileURLs property([react-native-webview#1730](react-native-webview#1730)) ([8d098ef](react-native-webview@8d098ef))
* fix:iOS13 scrollView.automaticallyAdjustsScrollIndicatorInsets default value YES which make the webview vertical indicator position in wrong offset * added types and doc * fix: breaking bug for props not include under iOS13 Co-authored-by: BillHsieh <[email protected]> Co-authored-by: xietian <[email protected]> Co-authored-by: Thibault Malbranche <[email protected]> Co-authored-by: Thibault Malbranche <[email protected]>
## [11.2.1](react-native-webview/react-native-webview@v11.2.0...v11.2.1) (2021-01-25) ### Bug Fixes * **ios:** error on iOS < 13([react-native-webview#1843](react-native-webview#1843)) ([283fe12](react-native-webview@283fe12))
…iew#1768) * Upgrade react-native-windows to 0.63.11 * Downgrade to 0.62.17
## [11.2.2](react-native-webview/react-native-webview@v11.2.1...v11.2.2) (2021-02-10) ### Bug Fixes * **windows:** Resolve Deploy Issue ([react-native-webview#1850](react-native-webview#1850)) ([ad702f5](react-native-webview@ad702f5))
…iew#1748 by @cristianoccazinsp) Co-authored-by: Cristiano Coelho <[email protected]> Co-authored-by: Thibault Malbranche <[email protected]>
## [11.2.3](react-native-webview/react-native-webview@v11.2.2...v11.2.3) (2021-02-11) ### Bug Fixes * **android:** Fix full=screen video when in modals ([react-native-webview#1748](react-native-webview#1748) by [@cristianoccazinsp](https://github.com/cristianoccazinsp)) ([4f469ee](react-native-webview@4f469ee))
) * iOS cookie available for resource requests * Missig brace added Co-authored-by: niwani <[email protected]>
## [11.2.4](react-native-webview/react-native-webview@v11.2.3...v11.2.4) (2021-03-10) ### Bug Fixes * **iOS:** Send cookies with resource requests ([react-native-webview#1803](react-native-webview#1803)) ([1f089ba](react-native-webview@1f089ba))
Co-authored-by: sunzhongliang <[email protected]>
## [11.2.5](react-native-webview/react-native-webview@v11.2.4...v11.2.5) (2021-03-15) ### Bug Fixes * **iOS:** webview retain cycle ([react-native-webview#1916](react-native-webview#1916)) ([30a53d9](react-native-webview@30a53d9))
## [11.2.6](react-native-webview/react-native-webview@v11.2.5...v11.2.6) (2021-03-16) ### Bug Fixes * **ios:** Add missing nullability specifiers; fix if block warning ([react-native-webview#1898](react-native-webview#1898)) ([85dfca8](react-native-webview@85dfca8))
…t-native-webview#1662) * Add support for iOS-specific prop `limitsNavigationsToAppBoundDomains` * Add check for `limitsNavigationsToAppBoundDomains` property Turns out that @available is simply bugged right now in Xcode and will pretty much always return `true`. Adding a check for the property actually existing as well will avoid iOS <14 crashing horribly. * Improve documentation Co-authored-by: Thibault Malbranche <[email protected]>
# [11.3.0](react-native-webview/react-native-webview@v11.2.6...v11.3.0) (2021-03-16) ### Features * **ios:** Add support for `limitsNavigationsToAppBoundDomains` ([react-native-webview#1662](react-native-webview#1662)) ([7decc5c](react-native-webview@7decc5c))
…ent.IsLoaded (react-native-webview#1858) Co-authored-by: Thibault Malbranche <[email protected]>
## [11.3.1](react-native-webview/react-native-webview@v11.3.0...v11.3.1) (2021-03-16) ### Bug Fixes * **windows:** Check UAP contract version before calling FrameworkElement.IsLoaded ([react-native-webview#1858](react-native-webview#1858)) ([ac8eb97](react-native-webview@ac8eb97))
* original_master: (94 commits) chore(release): 11.3.1 [skip ci] fix(windows): Check UAP contract version before calling FrameworkElement.IsLoaded (react-native-webview#1858) fix(android:) enable DRM protected content (react-native-webview#1862) chore(release): 11.3.0 [skip ci] feat(ios): Add support for `limitsNavigationsToAppBoundDomains` (react-native-webview#1662) chore(release): 11.2.6 [skip ci] fix(ios): Add missing nullability specifiers; fix if block warning (react-native-webview#1898) chore(release): 11.2.5 [skip ci] chore(docs): Clarify that navigationType and isTopFrame is iOS only (react-native-webview#1880) chore(docs): fixed "postMessage" url in Reference.md (react-native-webview#1913) fix(iOS): webview retain cycle (react-native-webview#1916) chore(release): 11.2.4 [skip ci] fix(iOS): Send cookies with resource requests (react-native-webview#1803) chore(release): 11.2.3 [skip ci] fix(android): Fix full=screen video when in modals (react-native-webview#1748 by @cristianoccazinsp) chore(release): 11.2.2 [skip ci] fix(windows): Resolve Deploy Issue (react-native-webview#1850) chore(ci): Upgrade react-native-windows to 0.62.17 (react-native-webview#1768) chore(release): 11.2.1 [skip ci] fix(ios): error on iOS < 13(react-native-webview#1843) ...
* master: (186 commits) chore(release): 11.3.1 [skip ci] fix(windows): Check UAP contract version before calling FrameworkElement.IsLoaded (react-native-webview#1858) fix(android:) enable DRM protected content (react-native-webview#1862) chore(release): 11.3.0 [skip ci] feat(ios): Add support for `limitsNavigationsToAppBoundDomains` (react-native-webview#1662) chore(release): 11.2.6 [skip ci] fix(ios): Add missing nullability specifiers; fix if block warning (react-native-webview#1898) chore(release): 11.2.5 [skip ci] chore(docs): Clarify that navigationType and isTopFrame is iOS only (react-native-webview#1880) chore(docs): fixed "postMessage" url in Reference.md (react-native-webview#1913) fix(iOS): webview retain cycle (react-native-webview#1916) chore(release): 11.2.4 [skip ci] fix(iOS): Send cookies with resource requests (react-native-webview#1803) chore(release): 11.2.3 [skip ci] fix(android): Fix full=screen video when in modals (react-native-webview#1748 by @cristianoccazinsp) chore(release): 11.2.2 [skip ci] fix(windows): Resolve Deploy Issue (react-native-webview#1850) chore(ci): Upgrade react-native-windows to 0.62.17 (react-native-webview#1768) chore(release): 11.2.1 [skip ci] fix(ios): error on iOS < 13(react-native-webview#1843) ... # Conflicts: # android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java # apple/RNCWebView.h # apple/RNCWebView.m # docs/Reference.md # index.d.ts # yarn.lock
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Android 31 build pass, remove setAppCacheEnabled method