Open Bug 1843241 Opened 1 year ago Updated 1 year ago

after request fullscreen on an element after already being in fullscreen (F11), zooming in then exiting will break page layout

Categories

(Core :: Layout, defect)

Firefox 115
Desktop
Windows
defect

Tracking

()

Tracking Status
firefox-esr102 --- wontfix
firefox-esr115 --- wontfix
firefox115 --- wontfix
firefox116 --- wontfix
firefox117 --- fix-optional

People

(Reporter: eyalgruss, Unassigned)

References

(Regression)

Details

(Keywords: nightly-community, regression)

firefox 115.0.2 on windows 10 and 11

  1. go to https://eyalgruss.com/constrained/otomat
  2. press F11 for full screen
  3. right click the grid. this applies requestFullScreen on the element
  4. press ctrl+ a few times to zoom in
  5. press esc to exit full screen of the element
  6. the layout is broken - only the left part of the page is shown. you cannot recover by zooming out

Zoom here means reflow zoom. Moving to Layout.

Component: Panning and Zooming → Layout

I can reproduce this issue on Nightly117.0a1 Windows10.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5066eae18c2da8adecfa968a040b89af7acb138c&tochange=91fbc2fbea07511eb8f230f9d51142d22873e714

FYI, Fullscreen of video element is also affected.

Set release status flags based on info from the regressing bug 729011

:xidorn, since you are the author of the regressor, bug 729011, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(xidorn+moz)

If you move the cursor to the top of the screen to trigger the toolbar, the layout restores.

This indicates that bug 729011 may have regressed it because it removes an extra layout change on the chrome when exiting DOM fullscreen to browser full screen. But I think we should always be triggering a re-layout when exiting DOM fullscreen, regardless of whether the browser chrome changes the viewport.

If we disable such reflow on chrome (e.g. by completely suppress #fullscr-toggler in the browser chrome), there should probably be a real issue hidden behind causing the content not be reflowed properly.

Flags: needinfo?(xidorn+moz)

The severity field is not set for this bug.
:jfkthame, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jfkthame)
Severity: -- → S3
Flags: needinfo?(jfkthame)
You need to log in before you can comment on or make changes to this bug.