138569 2014-11-10 11:46:58 -0800 Hide all non-fullscreen elements when in fullscreen mode 2026-10-15 10:07:41 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 276855 1 jer.noble jer.noble dino fred.wang jonlee simon.fraser webkit-bug-importer oldest_to_newest 1047576 0 jer.noble 2014-11-10 11:46:58 -0800 Hide all non-fullscreen elements when in fullscreen mode 1047656 1 jer.noble 2014-11-10 15:11:11 -0800 rdar://problem/18912707 1047670 2 simon.fraser 2014-11-10 15:39:44 -0800 Does this destroy page state in a way that pages will detect (e.g. plug-in state)? 1047695 3 jer.noble 2014-11-10 16:51:30 -0800 Pages could detect state changes via window.getComputedStyle(), but this is already true of existing fullscreen UA styles. I don't know if destroying a plugin renderer by setting display:none will destroy that plug-in's state. 1047804 4 jonlee 2014-11-11 01:32:01 -0800 Would using 0 opacity be less destructive? 1047841 5 jer.noble 2014-11-11 08:12:47 -0800 Opacity:0 would not be enough. The elements would still get renderers, would still participate in layout, and could still force the backing store of their ancestors to become larger than the fullscreen element. 2262392 6 fred.wang 2026-10-12 00:48:38 -0700 Simon, Jer: Is this bug still valid? I'm unclear what the problem was about but I think these days fullscreen is implemented via https://drafts.csswg.org/css-position-4/#document-top-layer and I imagine that addresses these issues from 2014. 2262582 7 simon.fraser 2026-10-12 09:54:34 -0700 I think we can close it. 2262605 8 fred.wang 2026-10-12 10:36:35 -0700 (In reply to Simon Fraser (smfr) from comment #7) > I think we can close it. 👍🏼