Firefox Nightly window cannot be drag&dropped to relocate it on latest macOS 14 builds
Categories
(Core :: Widget: Cocoa, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | --- | unaffected |
firefox120 | blocking | verified |
People
(Reporter: vlucaci, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
2.60 MB,
video/quicktime
|
Details |
Found in
- 120.0a1 (build ID 20231001214422)
Affected versions
- 120.0a1 (build ID 20231001214422)
Tested platforms
- Affected platforms: macOS 14.1(23B5046f) and macOS 14(23A344)
- Unaffected platforms: macOS 10.15, macOS 11, macOS 12, macOS 13
Steps to reproduce
- Launch FF.
- Attempt to drag&drop the FF window anywhere to relocate it.
Expected result
- The FF window moves wherever the user takes it with the drag and drop action.
Actual result
- The window is unresponsive and cannot be relocated anywhere using the drag and drop action.
Regression range
Additional notes
- This issue does not reproduce for other browsers or applications.
- This issue does not reproduce for other FF builds(Release, beta or DevEd)
- This issue does not reproduce for other macOS build versions(other than 14 and 14.1).
- We consider this issue to be an S2 since a very basic and important functionality(moving a browser window anywhere) is no longer working.
Reporter | ||
Comment 1•2 years ago
|
||
Hello Mike,
it seems that 1855564 has caused this regression.
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1855564
Comment 3•2 years ago
|
||
I’m running macOS 14(23A344)
and I’m experiencing this bug
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 4•2 years ago
|
||
After further investigation, it turns out that this issue is indeed occurring for both macOS 14.1(23B5046f) and macOS 14(23A344).
Thank you Jonny.
Comment 6•2 years ago
|
||
[Tracking Requested - why for this release]: basic browser UI feature of broken on MacOS 14 (the latest version that just released).
Updated•2 years ago
|
Updated•2 years ago
|
Comment 7•2 years ago
|
||
requested backout bug 1855564 until this could be fixed
Comment 8•2 years ago
|
||
I hope this can be fixed before it hits beta or release. Many people's productivity will be severely impaired if it hits beta or release. It is much harder for me to work with Firefox in this state as I can't maximize screen estate or move my Firefox window to another screen. :-(
Comment 9•2 years ago
•
|
||
I hope this can be fixed before it hits beta or release
This is a release blocker. If this isn't an S1
I don't know what would be!
Comment 10•2 years ago
|
||
I can reproduce on Sonoma beta. I'll try to figure this out such that when Bug 1855564 finally sticks, we won't have this bad behavior.
Comment 11•2 years ago
|
||
We implement window dragging by setting up our NSView hierarchy in such a way that the NSViews in the back return YES
from movableByWindowBackground
, and then we place non-movable transparent NSViews in the non-movable regions of the window (they return NO
from movableByWindowBackground
). See here for more details.
We also have a hack here to avoid paints which might be causing problems and which might be unnecessary these days.
Comment 12•2 years ago
|
||
When debugging this, I suggest the following approach: First, try to remove the call to ManipulateViewWithoutNeedingDisplay
(just call mNonDraggableRegion.UpdateRegion
directly). If that doesn't fix it, dump the NSView hierarchy starting at the window's border view ([[window contentView] superview]
) along with each view's movableByWindowBackground
property. There may also be a NSWindow
styleMask flag that affects this behavior.
Comment 13•2 years ago
|
||
Adjusting Priority and Severity since bug 1855564 has been backed out.
Updated•2 years ago
|
Comment 14•2 years ago
|
||
Fixed by backout of bug 1855564. Follow-up work will happen in bug 1856452.
Updated•2 years ago
|
Reporter | ||
Comment 15•2 years ago
|
||
Confirming this issue as verified fixed on 120.0a1(20231002221644) using macOS 14.1(23B5046f) and 14(23A344)
Comment 16•2 years ago
|
||
It works like a charm! Thanks for fixing this so quickly. Team Firefox is fantastic! <3
Description
•