Sharing bar cannot be minimized when Firefox is built with the macOS 11 SDK
Categories
(Core :: Widget: Cocoa, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox94 | --- | unaffected |
| firefox95 | --- | unaffected |
| firefox96 | --- | disabled |
| firefox97 | --- | fixed |
| firefox101 | --- | fixed |
People
(Reporter: btham, Assigned: spohl)
References
Details
Attachments
(2 files)
Steps to reproduce:
I am filing this on behalf of someone else, who has an M1 iMac running macOS Big Sur 11.6 and Firefox 94.0.1. They report that the issue happens 100% of the time, but on my own personal Macbooks, I don't have this issue, so it may only affect some Mac models.
- On Firefox, open https://webrtc.github.io/samples/src/content/getusermedia/getdisplaymedia/.
- Start sharing content.
- Try to minimize the float bar that appears.
Actual results:
Float bar cannot be minimized.
Expected results:
Float bar is minimized.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Site Permissions' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Can't reproduce on Ubuntu 21.10 and my Catalina macOS VM.
Could you elaborate on "Float bar cannot be minimized"? Does nothing happen when the minimize button is pressed? A screen recording could also help to diagnose this issue.
This doesn't seem directly SitePermissions related so I'm moving it to Widget.
| Assignee | ||
Comment 3•3 years ago
|
||
I'm not currently able to reproduce this either. Could you provide a screen recording of the issue?
Comment 4•3 years ago
|
||
:timhuang was able to reproduce this on macOS. I can now also reproduce in my macOS VM on Nightly. Seems to be a recent regression, since I can't reproduce on release.
The minimize button of the WebRTC screen sharing indicator window reacts to clicks but doesn't minimize the window.
Comment 5•3 years ago
|
||
Mike, could this be related to your patch for Bug 1732572?
Comment 6•3 years ago
|
||
I just did a mozregression:
53:47.48 INFO: Narrowed integration regression window from [78b7f5ef, 572b175e] (4 builds) to [ca239a52, 572b175e] (2 builds) (~1 steps left)
53:47.48 INFO: No more integration revisions, bisection finished.
53:47.48 INFO: Last good revision: ca239a52bff698c5349389675c1af7a83553b523
53:47.48 INFO: First bad revision: 572b175efb0960eb15cc814d9c8f8f65afecae52
53:47.48 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ca239a52bff698c5349389675c1af7a83553b523&tochange=572b175efb0960eb15cc814d9c8f8f65afecae52
so this looks to have been introduced by the switch to the new macOS SDK.
Comment 7•3 years ago
|
||
Interesting! This explains why M1 Macs have always had this issue, but Intel Macs only as of a few days ago.
What's supposed to happen when the minimize button is clicked? Is the window supposed to minimize into the Dock?
Comment 8•3 years ago
|
||
(In reply to Markus Stange [:mstange] from comment #7)
Is the window supposed to minimize into the Dock?
The AppKit 10.13 release notes contain this:
The NSWindowStyleMaskMiniaturizable style mask bit is properly respected for applications that link on 10.13 or higher. Previously, it would only include showing or hiding the miniaturize button, but the window would potentially still be miniaturizable via menu items or double clicking on the titlebar.
So it sound like we're not specifying NSWindowStyleMaskMiniaturizable for this window, but should be.
Comment 9•3 years ago
|
||
Set release status flags based on info from the regressing bug 1696504
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
| Assignee | ||
Comment 10•3 years ago
|
||
Looking into this.
| Assignee | ||
Comment 11•3 years ago
|
||
Comment 12•3 years ago
|
||
Comment 13•3 years ago
|
||
| bugherder | ||
Comment 14•3 years ago
•
|
||
Any tips on how to reproduce this?
I'm testing on and intel mac with macOS 12.1 and SDK=11.0. After reverting this patch I can't repro the original bug where the dialog doesn't minimise :( trying to debug the regression, since it's pretty impactful for VO users
| Assignee | ||
Comment 15•3 years ago
|
||
(In reply to Morgan Reschenberg [:morgan] from comment #14)
Any tips on how to reproduce this?
I'm testing on and intel mac with macOS 12.1 and SDK=11.0. After reverting this patch I can't repro the original bug where the dialog doesn't minimise :( trying to debug the regression, since it's pretty impactful for VO users
Are you confident that you built with the macOS 11 SDK? I just confirmed on Intel macOS 12.3 that I'm able to reproduce the original bug here if Firefox is built with any macOS SDK newer than 10.12. Only macOS 10.12 didn't reproduce the issue reported here. More specifically, I was able to reproduce the issue with Firefox built with the macOS 10.13, 10.14, 10.15, 11.0 and 12.3 SDK.
Comment 16•3 years ago
•
|
||
(In reply to Stephen A Pohl [:spohl] from comment #15)
(In reply to Morgan Reschenberg [:morgan] from comment #14)
Any tips on how to reproduce this?
I'm testing on and intel mac with macOS 12.1 and SDK=11.0. After reverting this patch I can't repro the original bug where the dialog doesn't minimise :( trying to debug the regression, since it's pretty impactful for VO usersAre you confident that you built with the macOS 11 SDK? I just confirmed on Intel macOS 12.3 that I'm able to reproduce the original bug here if Firefox is built with any macOS SDK newer than 10.12. Only macOS 10.12 didn't reproduce the issue reported here. More specifically, I was able to reproduce the issue with Firefox built with the macOS 10.13, 10.14, 10.15, 11.0 and 12.3 SDK.
Yep. I was building with 10.14 before and couldn't reproduce -- just upgraded yesterday to 11.0. For reference, this is my mozconfig:
ac_add_options --enable-debug --enable-optimize --enable-debug-symbols
ac_add_options --enable-application=browser
mk_add_options AUTOCLOBBER=1
ac_add_options --with-macos-sdk=$HOME/SDK-archive/MacOSX11.0.sdk/
ac_add_options --with-ccache=sccache
I can try with another SDK, though, I have 10.13 locally. I'll also update to 12.2.
| Reporter | ||
Comment 17•3 years ago
|
||
We are still seeing this issue in Firefox 98.0.1, even though this bug has been marked as resolved. Has the issue really been fixed?
Updated•3 years ago
|
| Assignee | ||
Comment 18•3 years ago
|
||
(In reply to btham from comment #17)
We are still seeing this issue in Firefox 98.0.1, even though this bug has been marked as resolved. Has the issue really been fixed?
Could you please confirm that you are able to reproduce using the steps from comment 0? Or do you have different steps to reproduce?
| Reporter | ||
Comment 19•3 years ago
|
||
Yes, it can be reproduced with the same steps. If it helps, the machine that that we are using to reproduce this issue is an 8GB M1 iMac (24-inch, 2021) running macOS Monterey 12.1.
| Assignee | ||
Comment 20•3 years ago
|
||
Comment 21•3 years ago
|
||
Comment 22•3 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 23•3 years ago
|
||
Would you be able to confirm that this is now fixed for you as well (as of tomorrow's nightly build, April 6th)?
| Reporter | ||
Comment 24•3 years ago
|
||
Apologies for the delayed response. I've asked the person who is having this issue to try to reproduce it on Firefox Nightly and will have a response soon.
| Reporter | ||
Comment 25•3 years ago
|
||
We've tested on Nightly version 101.0a1 and the issue no longer occurs. Thanks for your help!
| Assignee | ||
Comment 26•3 years ago
|
||
(In reply to btham from comment #25)
We've tested on Nightly version 101.0a1 and the issue no longer occurs. Thanks for your help!
Glad to hear it. Thanks for verifying!
Description
•