233532 2021-11-26 16:04:38 -0800 All contents in an inert frame should also be inert 2022-02-11 13:06:43 -0800 1 1 1 Unclassified WebKit Frames WebKit Nightly Build Unspecified Unspecified RESOLVED WONTFIX https://bugzilla.mozilla.org/show_bug.cgi?id=1743215 https://bugs.webkit.org/show_bug.cgi?id=236512 InRadar P2 Normal --- 1 obrufau webkit-unassigned ntim webkit-bug-importer oldest_to_newest 1818010 0 obrufau 2021-11-26 16:04:38 -0800 See https://html.spec.whatwg.org/multipage/interaction.html#inert > While a browsing context container is marked as inert, its nested browsing context's active document, and all nodes in that Document, must be marked as inert. (A "browsing context container" is something like a <frame> or <iframe>) WebKit and Firefox don't do that. Chromium does. I plan to add a test in https://chromium-review.googlesource.com/c/chromium/src/+/3302812 1820338 1 webkit-bug-importer 2021-12-03 16:05:22 -0800 <rdar://problem/86038340> 1840503 2 ntim 2022-02-11 13:06:43 -0800 Closing given bug 236512