Closed Bug 1366240 Opened 7 years ago Closed 1 year ago

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

Categories

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

Product:
Core
Component:
Graphics: Text
Version:
55 Branch
Platform:
x86_64
Windows 7
Type:
defect

Tracking

()

Status:
RESOLVED INACTIVE
Tracking Flags:
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)

Firefox 54.png
(deleted), image/png
Details
Firefox 55.png
(deleted), image/png
Details 
[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.
Attached image Firefox 54.png (deleted) — 

  

  



    
    

    
  

      
      
      
      

        Attached image
          
        Firefox 55.png (deleted)
        — 
      

    


  

  

  



    
    

    
  
This is a regression from bug 653670. Bug 1364387 will fix this except when the location bar is overflowing.

  

  


Blocks: 653670
Depends on: 1364387
Keywords: regressionwindow-wanted

    
    

    
  
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.

  

  



          tracking-firefox55:
          ? → -

    
    

    
  
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?).

  

  



          status-firefox55:
          affected → fix-optional

    
    

    
  
(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).

  

  



          tracking-firefox55:
          - → ?

    
    

    
  
Ups, it's not fixed yet, I was seeing wrong bug.

  

  



          tracking-firefox55:
          ? → ---

    
    

    
  
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.

  

  



          status-firefox60:
          fix-optional → wontfix

          status-firefox61:
          affected → wontfix

          status-firefox62:
          affected → fix-optional

    
    

    
  
Too late to fix in 63. We could still take a patch for 65 and potentially for 64.

  

  



          status-firefox63:
          affected → wontfix

          status-firefox64:
          affected → fix-optional

    
    

    
  
Another one that is just going to be backlog. We would take a patch but don't need to keep triaging it.

  

  



          status-firefox65:
          affected → fix-optional

          status-firefox66:
          --- → fix-optional

    
    

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



  

  



          status-firefox68:
          --- → affected

    
    

    
  
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)

    
    

    
  
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)
Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(lsalzman)
Resolution: --- → INACTIVE

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: