Closed
Bug 1081679
Opened 10 years ago
Closed 8 years ago
Ignore very thin fills without strokes
Categories
(Firefox Graveyard :: Shumway, defect)
Firefox Graveyard
Shumway
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: till, Unassigned)
References
Details
Attachments
(1 file)
88 bytes,
application/x-shockwave-flash
|
Details |
The Flash vector renderer doesn't render anything for very thin stroke-less fills. If the fill's width (or height) doesn't exceed 2 twips, it's simple not drawn at all. We draw a very thin-appearing interpolation. The attached SWF is a reduced test case, but the issue does occur in the real world. Example: http://swf.codeazur.com.br/#0a1bda375c17fcbdb7d67124a94599c5d050cb9646230677413225eb5fd612a2 I'm not sure how we can deal with this while using the Canvas2D rasterizer. With our own rasterizer, we could just ignore edges that are too close together, one scanline at a time.
Reporter | ||
Comment 1•10 years ago
|
||
Oh, to be sure, in the SWF archive example this issue isn't all that visible: it affects grey lines at the left and right borders of the SWF, which aren't really obvious if you don't look *really* closely.
Comment 2•10 years ago
|
||
I see much larger problem here, namely a triangular gray overlay. Do you not see this?
Reporter | ||
Comment 3•10 years ago
|
||
(In reply to Michael Bebenita [:mbx] from comment #2) > I see much larger problem here, namely a triangular gray overlay. Do you not > see this? I see it, but it's an independent issue, which I'm investigating. Sorry, I should've made that clear.
Comment 4•10 years ago
|
||
Till says there's not much we can do about this without writing our own rasterizer to implement Flash's behavior.
Blocks: shumway-1.0
Updated•9 years ago
|
Blocks: shumway-later
Comment 5•9 years ago
|
||
This bug does not need to block Shumway's 1.0 milestone for ads.
No longer blocks: shumway-1.0
Assignee | ||
Updated•8 years ago
|
Product: Firefox → Firefox Graveyard
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•