Open Bug 1366240 Opened 5 years ago Updated 11 months ago

Grayscale antialiasing instead of subpixel antialiasing is used in address bar after landing patches from bug #653670

Categories

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

55 Branch
x86_64
Windows 7
defect

Tracking

()

Tracking Status
firefox-esr45 --- unaffected
firefox-esr52 --- unaffected
firefox-esr60 --- wontfix
firefox53 --- unaffected
firefox54 --- unaffected
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 --- verified
firefox68 --- wontfix

People

(Reporter: Virtual, Unassigned)

References

(Blocks 1 open bug)

Details

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

Attachments

(2 files)

[Tracking Requested - why for this release]: Regression


STR.
1. Open Firefox
2. and see address bar font text rendering


I suspect it's regression due to some recent Photon address bar changes, which I'm yet to found in detail which one is the main cause.
This is a regression from bug 653670. Bug 1364387 will fix this except when the location bar is overflowing.
Blocks: 653670
Depends on: 1364387
Thank you very much Dão Gottwald [::dao] for finding specific bug which caused this issue.
Has Regression Range: --- → yes
Has STR: --- → yes
Keywords: meta
Priority: -- → P3
Whiteboard: [gfx-noted]
Summary: Grayscale antialiasing instead of subpixel antialiasing is used in address bar on Mozilla Firefox Nightly 55.0a1 → Grayscale antialiasing instead of subpixel antialiasing is used in address bar after landing patches from bug #653670
Doesn't seem worth tracking for 55 release.
Sounds like this is mostly fixed in 55. We could close this issue and file a new bug for the specific case mentioned in comment 3 (maybe make it a good first bug?).
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #6)
> Sounds like this is mostly fixed in 55. We could close this issue and file a
> new bug for the specific case mentioned in comment 3 (maybe make it a good
> first bug?).

Bug 1366405 should help further. The rest isn't really fixable, let alone as a good first bug.
Depends on: 1366405
There is always the option to back out the offending patch.

Mozilla should not add the features with not fixed regressions, especially the ones which causes the bad text font rendering and the eye strain because of it.
[Tracking Requested - why for this release]: Rerequesting tracking, as fixed bug #1366405 unfortunately didn't make any difference to this issue (at least in my case).
I get this is still an issue and is annoying on Win 7 for some folks, but I don't think changing the flags on all the related bugs at once is going to make it more of a priority. 

Happy to take a patch in Nightly if anyone can work on this, but it isn't a release blocker.
Too late to fix in 63. We could still take a patch for 65 and potentially for 64.
Another one that is just going to be backlog. We would take a patch but don't need to keep triaging it.

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

Hi,

I get the impression that we can close this bug. Have you had this issue lately?

Regards, Flor.

Flags: needinfo?(Virtual)

Unfortunately, I can still reproduce this issue in Mozilla Firefox Nightly 87.0a1 (2021-02-04).

Flags: needinfo?(Virtual)
You need to log in before you can comment on or make changes to this bug.