Closed Bug 1567713 Opened 5 years ago Closed 2 years ago

Grayscale antialiasing instead of subpixel antialiasing is used in address bar on hovering background tabs for moment on Mozilla Firefox Nightly 57.0a1 (2017-09-20)

Categories

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

57 Branch
x86_64
Windows 7
defect

Tracking

()

VERIFIED WORKSFORME
Tracking Status
firefox-esr60 --- wontfix
firefox-esr68 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- wontfix
firefox72 --- wontfix
firefox73 --- wontfix
firefox74 --- wontfix
firefox75 --- fix-optional
firefox76 --- fix-optional
firefox116 --- unaffected

People

(Reporter: Virtual, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(4 keywords)

Attachments

(1 file)

STR:

  1. Open New Tab
  2. Open this website page - https://mailfence.com/
  3. Hover background tabs
    and see that for moment grayscale antialiasing instead of subpixel antialiasing is used in address bar

Latest good build:
https://archive.mozilla.org/pub/firefox/nightly/2017/09/2017-09-20-10-04-26-mozilla-central/

First bad build:
https://archive.mozilla.org/pub/firefox/nightly/2017/09/2017-09-20-22-04-31-mozilla-central/

Regression range pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a20de99fa3c1ba6287fe47d493a859a4e95120b0&tochange=319a34bea9e4f3459886b5b9e835bd338320f1fd

I suspect that it could be caused by:
bug #1399498

mozregression-gui failed me for looking for specific bug which caused this regression, as it's probably too old.

@ Johann Hofmann [:johannh] - I suspect that your patch caused this regression, could you please look on this or it's missed call? Thanks!

Flags: needinfo?(jhofmann)
Attached video screencast.mp4 (deleted) β€”
Priority: -- → P3

To be honest I can't really tell if it was my patch that caused this, it might, but I'm certainly not an expert on text rendering. This is in the right component and I guess folks will eventually get around to it.

Thanks :)

Flags: needinfo?(jhofmann)
Keywords: access

Hi,
We tried to get a different regression range for this issue but were getting the not enough data to bisect error. We are removing the regression - range keyword since its already been provided in the description of this issue.

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 auto_nag documentation.

Flags: needinfo?(lsalzman)
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(lsalzman)
Resolution: --- → INACTIVE

I would like to inform that the issue does not occur anymore in Mozilla Firefox 116.0a1 (2023-06-16), so I am marking this issue as WORKSFORME.

Status: RESOLVED → VERIFIED
Resolution: INACTIVE → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: