Closed Bug 1379295 Opened 7 years ago Closed 7 years ago

[macOS] Show all history sidebar (using vibrancy on osx) is unreadable when using the default theme

Categories

(Core :: Graphics: WebRender, defect, P3)

defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox56 --- unaffected
firefox57 --- unaffected

People

(Reporter: marcia, Assigned: mstange)

References

Details

(Whiteboard: [gfx-noted])

Attachments

(1 file, 2 obsolete files)

Seen while running Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:55.0) Gecko/20100101 Firefox/55.0 ID:20170706085508 CSet: 1ae7e516e5dae3c0b537251781e1adeb50783131

Webrender is enabled in this profile.

STR:
1. At some point I switched themes from Ocean Ice back to the default theme. Restarted Nightly.
2. History | Show All History - observe the attached screenshot.

In the last hour I upgraded my machine from 10.12 -> 10.13, so that is the only major change made to this machine.

Not able to yet reproduce in another nightly profile on the same machine.
I see the same thing if I set gfx.webrender.enabled to true.

Looks like it breaks -moz-mac-vibrancy
Markus, I don't know where this goes on the cocoa/webrender/graphics spectrum - can you help triage / find an owner if this is something we intend to ship (haven't stayed on top of webrender, I'm afraid) ? :-)
Component: Theme → Widget: Cocoa
Flags: needinfo?(mstange)
Product: Firefox → Core
Summary: Show all history pane is unreadable after switching back to default theme on Nightly Mac → [macOS] Show all history sidebar (using vibrancy on osx) is unreadable when using the default theme
This falls squarely within the graphics/webrender component: WebRender needs to support OP_SOURCE on ColorLayers.

This requires https://github.com/servo/webrender/issues/1416 .
Blocks: webrender
Component: Widget: Cocoa → Graphics: WebRender
Flags: needinfo?(mstange)
Whiteboard: [gfx-noted]
Attachment #8921165 - Attachment is obsolete: true
Attachment #8921724 - Attachment is obsolete: true
With layers-free, sidebars are no longer unreadable. I'm going to use bug 1386162 for implementing vibrancy with WebRender.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Assignee: nobody → mstange
Resolution: WORKSFORME → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: