Top-level document blocking modal should not be applied to iframes #14826
Labels
feature/shields/adblock
Blocking ads & trackers with Shields
OS/Android
Fixes related to Android browser functionality
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
privacy-pod
Feature work for the Privacy & Web Compatibility pod
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-macOS
QA/Yes
release-notes/exclude
Milestone
The "suspicious site ahead" modal should not be rendered in iframes that are blocked - the "Proceed" and "Go back" buttons do not do anything, and filter lists are not designed to block "potentially useful" frames.
Eventually, these should be hidden, but in the meantime it's better to render them with the less-conspicuous "broken document" page that is default in Chromium (and was the behavior before top-level-document blocking was implemented).
The text was updated successfully, but these errors were encountered: