Closed
Bug 1381291
Opened 7 years ago
Closed 5 years ago
[macOS 10.13] If building with 10.13 SDK, toolbar of standalone windows is not uniform
Categories
(Core :: Widget: Cocoa, defect, P4)
Core
Widget: Cocoa
Tracking
()
RESOLVED
DUPLICATE
of bug 1533562
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: Nomis101, Unassigned)
Details
(Whiteboard: tpi:+)
Attachments
(1 file)
63.64 KB,
image/jpeg
|
Details |
If Firefox/Thunderbird is build on 10.13 using the 10.13 SDK, the top of the toolbar of standalone windows will look darker. As can be seen in the screenshots.
Updated•7 years ago
|
Priority: -- → P4
Whiteboard: tpi:+
Comment 1•7 years ago
|
||
Does this also happen when building with the 10.11 SDK?
Flags: needinfo?(Nomis101)
No, it only happens if building with the 10.13 SDK.
Flags: needinfo?(Nomis101)
Comment 3•7 years ago
|
||
Thanks.
Updated•7 years ago
|
status-firefox57:
--- → wontfix
Comment 4•7 years ago
|
||
Per comment 2, this shouldn't block our highsierra meta bug since we're not going to start building with the 10.13 SDK anytime soon.
No longer blocks: highsierra
Comment 5•7 years ago
|
||
I took a look at your screenshot and I'm not sure what I'm looking at. Is this meant to compare the light and the dark toolbar? They look pretty identical to me. Also, have you tried building with the 10.11 SDK on macOS 10.13 (comment 1)? I'm asking because I just gave it a shot and ran into compile errors that prevented me from building successfully.
Flags: needinfo?(Nomis101)
It does not compare, it is just a screenshot of the Page info window and the Library window after building with the 10.13 SDK. I have tried to build with all SDKs, from 10.9 to 10.13 on macOS 10.13. But since two weeks I have some problems to build using the 10.13 SDK, don't know why, need to sort that out.
Flags: needinfo?(Nomis101)
Comment 7•5 years ago
|
||
Is this still happening? I've done a local build with 10.13 SDK and I dont' see the separation on Page Info (everything is the same color)
Comment 8•5 years ago
|
||
Oh, I probably fixed this with bug 1533562 then!
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•