Bug 138569
| Summary: | Hide all non-fullscreen elements when in fullscreen mode | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jer Noble <jer.noble> |
| Component: | New Bugs | Assignee: | Jer Noble <jer.noble> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | dino, fred.wang, jonlee, simon.fraser, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 276855 | ||
Jer Noble
Hide all non-fullscreen elements when in fullscreen mode
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jer Noble
rdar://problem/18912707
Simon Fraser (smfr)
Does this destroy page state in a way that pages will detect (e.g. plug-in state)?
Jer Noble
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.
Jon Lee
Would using 0 opacity be less destructive?
Jer Noble
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.
Frédéric Wang Nélar
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.
Simon Fraser (smfr)
I think we can close it.
Frédéric Wang Nélar
(In reply to Simon Fraser (smfr) from comment #7)
> I think we can close it.
👍🏼