Taskbar/Startmenu block in maximized firefox
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
People
(Reporter: sj.vegetto, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:141.0) Gecko/20100101 Firefox/141.0
Steps to reproduce:
Start Firefox maximized window 11 autohide of taskbar does not pop up over firefox 141.xx (was fine on 140.xx till 141.xx was autoupdated too), This was issue back with 137.xx and was later fixed with 138.xx
Expected results:
Taskbar/starbar should pop up over Firefox when "Maximized"
temp fix is to Minimize then maximize firefox and the taskbar/startbar will pop up over firefox till firefox is restarted
other fix I found which more permanent
About:config
widget.windows.fullscreen_marking_method
2 is defualt
1 make the taskbar/startbar pop up over firefox maximized correctly each and ever time I launch it
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Shell Integration' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 year ago
|
||
:handyman any idea who to forward this too as :rkraesig is not available?
Comment 3•1 year ago
|
||
We're dealing with this for Windows 10 in bug 1957069. This is the first report that it can happen on Windows 11.
Updated•1 year ago
|
| Reporter | ||
Comment 4•11 months ago
|
||
This not fix so dont know why labed at resloved fixed.
141.02 has same issue"widget.windows.fullscreen_marking_method" it defualt to 2
0=fixed
1= Partial fixed so long you never use F11 to fullscreen once you hit F11 again starbar will no longer pop up over firefox if auto hide is enabled.
Thunderbird also defualts to 0 for setting and has never had this issue. Last time Firefox has this issue was 137.xx that 138.xx fixed was fine with 138 to 140.xx builds till it was changed again with 141.xx
Step to produce are still exaclty the same, and does it multiple systems
| Reporter | ||
Updated•11 months ago
|
Comment 5•11 months ago
|
||
That was likely an accident, this should be resolved duplicate of Bug 1957069.
Description
•