Bug 233532

Summary:	All contents in an inert frame should also be inert
Product:	WebKit	Reporter:	Oriol Brufau <obrufau>
Component:	Frames	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED WONTFIX
Severity:	Normal	CC:	ntim, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified
See Also:	https://bugzilla.mozilla.org/show_bug.cgi?id=1743215 https://bugs.webkit.org/show_bug.cgi?id=236512

Oriol Brufau

Reported 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

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2021-12-03 16:05:22 PST

Tim Nguyen (:ntim)

Comment 2 2022-02-11 13:06:43 PST

Closing given bug 236512

Note You need to log in before you can comment on or make changes to this bug.