Closed Bug 596251 Opened 15 years ago Closed 12 years ago

Incorrect rendering of SVG gradients under Direct2D

Categories

(Core :: Graphics, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: the.decryptor, Assigned: bas.schouten)

References

Details

Attachments

(4 files)

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7pre) Gecko/20100914 Firefox/4.0b7pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7pre) Gecko/20100914 Firefox/4.0b7pre At certain sizes, gradients in SVG files can be drawn as if they were in the wrong position (i.e. they draw in the correct position, but with the offsets and positions set like they start further to the left or right, etc.), or vanish entirely in SVG files when using Direct2D. It can also be seen when zooming in or out while displaying the SVG file (via <object> or <img>) When linking to the SVG file via an <img> tag, the drag image generated by dragging doesn't display the issue. Reproducible: Always
When displaying the file normally, zooming in and out a couple of steps causes the monkey's mouth to vanish. The mouth doesn't show for me when it's loaded via an <img> tag.
Blocks: d2d
blocking2.0: --- → ?
Attached image Another gradient issue.
I just noticed this test file I created a while ago also has a drawing issue with the gradient.
Bas says he sees differences between GDI and D2D. Alex, can you post screenshots of what you see when the rendering goes wrong?
Assignee: nobody → bas.schouten
Status: UNCONFIRMED → NEW
blocking2.0: ? → ---
Ever confirmed: true
Attached image Monkey Comparison
Here's what I see zooming into the Monkey emoticon by 2 steps. Top is D2D's rendering, bottom is GDI's rendering (Well, I think pixman is responsible in this mode)
This is at normal 100% zoom. Left is D2D, right is GDI.
The monkey now looks fine, but "Another gradient issue" looks very different, D2D vs pixman/gdi.
Unsurprisingly, it looks the same, cairo-d2d vs azure-d2d; this might change when we've got SVG using Azure directly.
This seems fine. Both Firefox 17 and Firefox 19 display the expected result.
On Windows 7, both examples work OK, with and without HWA.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: