Bug 233532 - All contents in an inert frame should also be inert
Summary: All contents in an inert frame should also be inert
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Frames (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-11-26 16:04 PST by Oriol Brufau
Modified: 2022-02-11 13:06 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oriol Brufau 2021-11-26 16:04:38 PST 
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
Comment 1 Radar WebKit Bug Importer 2021-12-03 16:05:22 PST 
<rdar://problem/86038340>
Comment 2 Tim Nguyen (:ntim) 2022-02-11 13:06:43 PST 
Closing given bug 236512