Closed
Bug 1423213
Opened 7 years ago
Closed 7 years ago
Semi-transparent mask is not correctly applied in SVG on Windows when hardware acceleration is enabled
Categories
(Core :: Graphics, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1448667
Tracking | Status | |
---|---|---|
firefox59 | --- | affected |
People
(Reporter: xidorn, Unassigned)
Details
(Whiteboard: [gfx-noted][webcompat])
Attachments
(1 file, 1 obsolete file)
399 bytes,
image/svg+xml
|
Details |
Steps to reproduce:
1. open page http://benchmarksgame.alioth.debian.org/u64q/which-programs-are-fastest.html
2. see the charts, and compare the charts with that in other browsers or Firefox on other platforms
Expected result:
There should be grey language names vertically lied in each column, and there should be horizontal grey lines for each scale line.
Actual result:
There is no language names nor scale lines.
Comment 1•7 years ago
|
||
I cannot repro this in my local Mac. Maybe windows only problem?
Whiteboard: [gfx-noted]
Reporter | ||
Comment 2•7 years ago
|
||
Yes, it is. I forgot to mention that, it is also only reproducible when hardware acceleration is enabled and on Windows.
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Comment 3•7 years ago
|
||
This is a testcase simplified from that image. It seems that the issue is related to mask.
Reporter | ||
Comment 4•7 years ago
|
||
linearGradient in the previous testcase is not necessary. A mask with transparency is enough to show this issue.
Attachment #8973117 -
Attachment is obsolete: true
Reporter | ||
Updated•7 years ago
|
Component: Graphics: Layers → Graphics
Summary: Some SVG elements are not shown when hardware acceleration is enabled → Semi-transparent mask is not correctly applied in SVG on Windows when hardware acceleration is enabled
Reporter | ||
Updated•7 years ago
|
Whiteboard: [gfx-noted] → [gfx-noted][webcompat]
Reporter | ||
Comment 5•7 years ago
|
||
This seems to have been fixed by bug 1448667.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•