Closed
Bug 1743215
Opened 4 years ago
Closed 4 years ago
All contents in an inert frame should also be inert
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: Oriol, Unassigned)
Details
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 (https://webkit.org/b/233532) 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•4 years ago
|
||
A bit weird that that would affect even cross-origin subframes... Seems like you could observe whether the embedder element is inert which is a bit suspect.
Updated•4 years ago
|
Severity: -- → S3
| Reporter | ||
Comment 2•4 years ago
|
||
Yes, this was bad. I removed it from the spec and from Blink.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•