White square at bottom right in about:support when os compositor was enabled on Windows.
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: sotaro, Assigned: gw)
References
Details
Attachments
(3 files, 1 obsolete file)
I saw it with latest nightly.
STR
- [1] Start Firefox with os compositor enabled on Windows.
- gfx.webrender.compositor: true
- [2] Move to about:support
Actual result
- White square at bottom right in about:support.
- It seemed to happen when Firefox window was a certain size. Then if the problem does not happen, we could try resizing window horizontally.
Expected result
- No white square at bottom right
Reporter | ||
Comment 1•5 years ago
|
||
Screenshot when the white square appeared.
Reporter | ||
Comment 2•5 years ago
|
||
I tried mozregression, but I am not sure which change caused the problem.
./mach mozregression --good 2019-10-20 --pref gfx.webrender.all:true gfx.webrender.compositor:true -a about:support
Reporter | ||
Comment 3•5 years ago
•
|
||
There was another STR to cause white square.
STR
- [1] Start Firefox with os compositor enabled on Windows. But window is not maximized.
- gfx.webrender.compositor: true
- [2] Move to a page like about: support
- [3] Enable menu bar
- [4] Select "Find in This Page" in Edit menu.
Actual result
- White square at bottom in about:support. When window was not maximized, the issue did not happen.
- It seemed to happen when Firefox window was a certain size. Then if the problem does not happen, we could try resizing window horizontally or vertically.
Expected result
- No white square at bottom
Reporter | ||
Comment 4•5 years ago
|
||
From the symptom, it seemed that some tiles of content were not rendered.
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 5•5 years ago
|
||
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 6•5 years ago
|
||
:gw, can you reproduce the problem? Comment 3 was easy to reproduce. I could reproduce the issue on my all Win10 PCs.
Comment hidden (obsolete) |
Assignee | ||
Comment 8•5 years ago
|
||
Yes, I can reproduce this. I'll investigate today, thanks for the STR!
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 9•5 years ago
|
||
In Draw compositor mode, tiles are placed into a bucket based on
the tile kind and/or opacity. This simplifies the renderer code
for this mode, which uses the z-buffer to reject opaque tiles.
In native compositor mode, the tiles need to be submitted in the
correct draw order. Opacity is a property of the native surface,
and should not affect the order the tiles are added to the visual
tree of the native compositor.
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 12•5 years ago
|
||
Fix Verified [testday-20191220]
Description
•