Fix JS compatibility issue for legacy browsers #537
Merged
Conversation
This file contains 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
Guillembonet
approved these changes
Jun 12, 2024
mingaila
force-pushed
the
fix/legacy-browser-compatibility
branch
from
36aebfa
to
ad1695b
Compare
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.
This pull request addresses issues encountered in the Android node provider app when rendering dvpn-web within a WebView. The problem arises on older Android 9 and older due to certain code sections written using JavaScript ES6 syntax.
To resolve compatibility issues, this fix involves "downgrading" the affected code to ensure support for Chromium 66, thereby restoring functionality on devices using Android 9.