Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 84651]
[ID: 591562]
[ID: 591587]
[ID: 591666]
[ID: 85206]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
The Android WebView currently does not provide sufficient support for web content to properly handle E2E on Android. Specifically, it's not possible for web content to reposition itself based on insets for the status bar and bottom navigation buttons, and the existing support for positioning around display cutouts is insufficient.
With the removal of the `windowOptOutEdgeToEdgeEnforcement` flag, it's not possible for content shown in WebViews on Android 16 to prevent being displayed in occluded areas. This will break countless apps that rely on WebViews by making buttons and text inaccessible behind system UI areas.
Please work with the Android WebView team to make sure WebView content can properly support E2E before mandating it across all Android apps.