Open Bug 1370064 Opened 7 years ago Updated 5 months ago

Grayscale antialiasing instead of subpixel antialiasing is used in long tab titles after landing patches from bug #658467


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

53 Branch
Windows 7



Tracking Status
firefox-esr45 --- unaffected
firefox-esr52 --- unaffected
firefox-esr60 --- wontfix
firefox53 - wontfix
firefox-esr91 --- wontfix
firefox54 - wontfix
firefox55 - wontfix
firefox56 - wontfix
firefox57 --- wontfix
firefox58 --- wontfix
firefox59 --- wontfix
firefox60 --- wontfix
firefox61 --- wontfix
firefox62 --- wontfix
firefox63 --- wontfix
firefox64 --- wontfix
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- wontfix
firefox67.0.1 --- wontfix
firefox68 --- wontfix
firefox97 --- wontfix
firefox98 --- wontfix
firefox99 --- wontfix


(Reporter: Virtual, Unassigned)


(Blocks 1 open bug, Regression)


(4 keywords, Whiteboard: [gfx-noted][qa-not-actionable])


(1 obsolete file)

[Tracking Requested - why for this release]: Regression

1. Open this URL -
and see that grayscale antialiasing instead of subpixel antialiasing is used in long tab titles

Caused by:
bug 658467 - Fade out tab label on overflow instead of ellipsis. r=jaws ui-r=shorlander
Has Regression Range: --- → yes
Has STR: --- → yes
We are about to go to 54 RC. Mark 53/54 won't fix.
Depends on: 1366405
Severity: major → normal
Priority: -- → P3
Whiteboard: [gfx-noted]
As this has shipped in 2 releases already I'm going to call it fix-optional for 55.
Too late to fix in 63. We could still take a patch for 65 and potentially for 64.

Bulk change for all regression bugs with status-firefox67 as 'fix-optional' to be marked 'affected' for status-firefox68.

[bulk change 69 status -> --- b/c to stop re-triaging old regressions every release]

Triage Owners: please do not set release status tracking flags in new releases unless this bug will actually be worked on

Whiteboard: [gfx-noted] → [gfx-noted][qa-not-actionable]
No longer blocks: 658467
Regressed by: 658467

Set release status flags based on info from the regressing bug 658467

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --

The severity field is not set for this bug.
:lsalzman, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(lsalzman)
Severity: -- → S4
Flags: needinfo?(lsalzman)
Attachment #9385192 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.