Open Bug 1427220 Opened 8 years ago Updated 3 years ago

<svg:text>s with same pos but diff stroke not on top of each other

Categories

(Core :: SVG, defect, P3)

58 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: bugzilla.20.ppf, Unassigned)

Details

Attachments

(5 files)

Attached file stroke_demo.html
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 Build ID: 20171218174357 Steps to reproduce: 1. Go to https://bl.ocks.org/Herst/raw/a304caf946e59a7e34c24bd828fa0b3a/ or open the attached test case. 2. Click on the "paint-order" checkbox to switch between drawing the text twice to get the outline/glow effect and look for changes. Actual results: There is a difference between the two states toggled through the checkbox. It looks like in the case with the two <text> elements on top of each other (instead of using paint-order) the two text elements are not exactly on top each other (the black text is not centered inside the bright outline text with the thicker stroke). See also the screenshots. Reproduced on Windows and Linux. Expected results: The two cases should be indistinguishable, as is the case in Google Chrome (see screenshot).
Attached image Windows
Attached image Linux
Attached image Google Chrome
This looks like antialiasing at work. I don't think it's a bug.
Component: Untriaged → SVG
Product: Firefox → Core
Attached image Linux (detail)
> This looks like antialiasing at work. There is indeed an antialiasing difference between the two cases on Windows, in the double paint case subpixel antialiasing is used while in the paint-order there is only greyscale AA (as is the case in Linux in either case). I would argue that this is unexpected as well which is why I filled bug 1400663 in which IMHO you didn't quite understand the problem as well (I should have been more clear). To the problem, horizontal antialiasing cannot account for vertical differences and like I said in Chrome both case look the same. Please have a look at the attached detail view to see how the *vertical* alignment is not correct.
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: