Closed
Bug 1700643
Opened 3 years ago
Closed 2 years ago
[macOS] Exiting full screen while browser is shrink to minimum height displays enlarged elements on top of the browser
Categories
(Core :: Widget: Cocoa, defect, P3)
Tracking
()
People
(Reporter: atrif, Unassigned)
Details
(Whiteboard: [mac:fullscreen:native-affected][mac:fullscreen:nonnative-affected])
Attachments
(1 file)
|
5.58 MB,
video/quicktime
|
Details |
Affected versions
- 89.0a1 (20210324084848)
- 88.0b2 (20210323190052)
- 87.0 (20210318103112)
- 86.0.1 (20210310152336)
Affected platforms
- macOS 11.2.2
- macOS 10.15
Steps to reproduce
- Open firefox and resize the browser to the minimum height.
- Enter full screen and exit fullscreen.
Expected result
- No glitches are displayed.
Actual result
- When exiting fullscreen the animation displayed enlarged elements on top of the browser.
Regression range
- I will search for one ASAP if there is one.
Notes
- Attached a screen recording.
- This happens with native and non-native fullscreen as well.
|
Reporter | |
Updated•3 years ago
|
Has Regression Range: --- → no
Has STR: --- → yes
|
||
Updated•3 years ago
|
QA Whiteboard: [qa-regression-triage]
|
|
Reporter | |
Comment 1•3 years ago
|
||
Reproducible on macOS 10.12 with Firefox 24.0a1 (2013-05-20) as well. I think it's safe to assume that this issue is not a regression. Removing the flags.
Has Regression Range: no → ---
Keywords: regressionwindow-wanted
|
||
Comment 2•3 years ago
|
||
This also reproduces in Safari and may therefore be expected behavior from a platform perspective.
Priority: -- → P3
|
|
||
Updated•3 years ago
|
Whiteboard: [mac:fullscreen] → [mac:fullscreen:native-affected][mac:fullscreen:nonnative-affected]
|
||
Comment 3•2 years ago
|
||
I can confirm this is definitely desired behaviour. macOS remembers the size of the window prior to the full-screening. It doesn't seem logical to me to do it any other way?
Can this even be changed in FF to begin with?
|
|
||
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•