On an external monitor in a maximized Firefox window, can't select a tab with the cursor at the top of the screen
Categories
(Core :: Widget: Win32, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox143 | --- | unaffected |
| firefox144 | --- | unaffected |
| firefox145 | --- | fix-optional |
| firefox146 | --- | affected |
People
(Reporter: gstoll, Assigned: gstoll)
References
(Regression)
Details
(Keywords: regression)
I can't click tabs if I have my cursor at the top of the screen. Need to move it down by 3-4 pixels to be able to click the hit area. This happens only on external monitors, not the laptop screen. The caption buttons or new tab button are also not clickable.
mozregression points at bug 1947324.
Comment 1•1 month ago
|
||
Set release status flags based on info from the regressing bug 1947324
| Assignee | ||
Comment 2•1 month ago
|
||
On my external monitor, there's an extra 5 px of space in the titlebar that seems to be causing this. This seems to be caused by the call to put_ExtendsContentIntoTitleBar(true).
Comment 3•1 month ago
|
||
Set release status flags based on info from the regressing bug 1947324
| Assignee | ||
Comment 4•1 month ago
|
||
Using the Browser Toolbox Inspector, when the window is maximized and on my external monitor (may be an DPI thing), there is ~5 px at the top of the titlebar that Firefox isn't drawing on. (i.e. mousing over the top <html> tag doesn't highlight)
Calling SetPresenterKind(AppWindowPresenterKind_FullScreen) does not help.
Updated•23 days ago
|
Comment 6•8 hours ago
|
||
So i originally posted my own bug report but its been merged here.
I decided to try that widget.windows.windowsappsdk.enabled to false, and it also fixes my issue, but the strange thing is when i view photos with windows photo viewer, i have that big white line at the top of my screen on my 2nd monitor still, so its not just a firefox issue
Im thinking this is actually a windows 11 issue?
| Assignee | ||
Comment 7•7 hours ago
|
||
Removing the WS_BORDER style from our windows seems to fix this. I was going to only do this when our window is maximized, but even with an unmaximized window you can still drag/resize it, and this also seems to fix bug 1994918 so I'm going to try just turning it off everywhere and see what happens.
| Assignee | ||
Updated•7 hours ago
|
Description
•