Open Bug 1400663 Opened 7 years ago Updated 2 years ago

No subpixel AA when using paint-order

Categories

(Core :: Graphics: Text, defect, P3)

56 Branch
defect

Tracking

()

UNCONFIRMED
Tracking Status
firefox56 --- fix-optional
firefox57 --- fix-optional

People

(Reporter: bugzilla.20.ppf, Unassigned)

Details

(Whiteboard: [gfx-noted])

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170914024831

Steps to reproduce:

1. Go to https://bl.ocks.org/Herst/cea785948891831cee238861735492d0?x=393.394&y=154.369&k=0.369&fontSize=50&strokeWidth=7&fontFamily=sans-serif a demo page which compares using paint-order to drawing a text twice.

2. See that in Example 1 and 2 are in principle doing the same so the result should look the same but this isn't the case. Most notably greyscale anti-aliasing is used in Example 2, the one using SVGs paint-order so the stroke is drawn behind the fill (as opposed to Example 1 which simply draws text elements with identical content but one for the stroke and the other for the fill).
I suspect that's just an artifact of where exactly you happen to draw the text.
Component: Untriaged → Graphics: Text
Product: Firefox → Core
Priority: -- → P3
Whiteboard: [gfx-noted]
Attached image fxLin.png
Can't reproduce on my Linux Desktop BTW.
> I suspect that's just an artifact of where exactly you happen to draw the text.

No, as can be seen from the screenshots from bug 1427220 it even happens if you try to place the <svg:text>s on top of each other.

The screenshots of bug 1427220 also shows that the issue appears on Windows but not Linux. On Linux I am always getting greyscale antialiasing and in Google Chrome there is always subpixel AA.
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: