Bug 911876 - Firefox ignores rgba-order setting for subpixel rendering (always uses rgb)
Summary: Firefox ignores rgba-order setting for subpixel rendering (always uses rgb)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 23
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-16 10:06 UTC by Toon Verstraelen
Modified: 2016-12-20 12:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 12:35:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot demonstrating wrong rgba-order in firefox (147.94 KB, image/png)
2013-02-16 10:06 UTC, Toon Verstraelen
no flags Details
Openoffice test (65.39 KB, image/png)
2013-03-03 13:49 UTC, Toon Verstraelen
no flags Details
Test with upstream firefox (210.72 KB, image/png)
2013-03-03 13:50 UTC, Toon Verstraelen
no flags Details

Description Toon Verstraelen 2013-02-16 10:06:47 UTC
Created attachment 698108 [details]
screenshot demonstrating wrong rgba-order in firefox

Description of problem:

My lcd screen has bgr ordering of the pixels. When activating bgr subpixel rendering with the dconf-editor, Gnome applications render fonts correctly but firefox sticks to rgb ordering. (See screenshot.)

Version-Release number of selected component (if applicable):

Firefox: 18.0.2

How reproducible: always


Steps to Reproduce:

1. Use dconf-editor to set the following keys

"org.gnome.settings-daemon.plugins.xsettings" "hinting full"
"org.gnome.settings-daemon.plugins.xsettings" "antialiasing" "rgba"
"org.gnome.settings-daemon.plugins.xsettings" "rgba-order" "bgr"

2. Open firefox and take a screenshot

3. Open the screenshot in the gimp and zoom in to 16x.
  

Actual results:

The wrong order can be noticed by the red edges on the left and the blue edges on the right of text, e.g. in the menu bar. Without magnification, this limits the readability of fonts in firefox.

Expected results:

There should be blue edges on the left and red on the right of text. This can be found in the window title bar where gnome controls the font rendering.


Additional info: a screenshot showing firefox and a gtk application with wrong and right ordering, respectively.

Comment 1 Martin Stransky 2013-02-18 09:10:35 UTC
Firefox still runs as a GTK2 application...does this settings affect other gtk2 apps? Like Open Office or so?

Comment 2 Martin Stransky 2013-02-26 08:49:55 UTC
Anyway, can you test a binary package from upstream? (from mozilla.com)

Comment 3 Toon Verstraelen 2013-03-03 13:49:08 UTC
Sorry for the late feedback. It works properly in openoffice. The upstream firefox packages just uses grayscale font-smoothing. (Two screenshots will be attached.)

Comment 4 Toon Verstraelen 2013-03-03 13:49:57 UTC
Created attachment 704549 [details]
Openoffice test

Proper bgr font rendering

Comment 5 Toon Verstraelen 2013-03-03 13:50:40 UTC
Created attachment 704550 [details]
Test with upstream firefox

grayscale font smoothing

Comment 6 Martin Stransky 2013-03-18 16:10:15 UTC
I guess it's because org.gnome.settings-daemon.plugins.xsettings is ignored by gtk_init() which comes from gtk2. So we may need to set it by hand untill gtk3 firefox is ready.

https://developer.gnome.org/gtk3/unstable/GtkSettings.html#GtkSettings--gtk-xft-rgba

Comment 7 Martin Stransky 2013-03-19 12:13:38 UTC
Which system do you run, screen resolution and so? Can you reproduce it in fallback mode too? Which video driver do you have? Because I'm unable to reproduce it on Fedora 18.

Comment 8 Martin Stransky 2013-03-19 12:14:35 UTC
Do you have any special settings? Like dpi, font settings/sizes or so?

Comment 9 Martin Stransky 2013-03-19 12:21:15 UTC
Anyway, my stock Firefox from Fedora 18 uses grayscale font smoothing (as well as the rest of whole desktop). 

The "org.gnome.settings-daemon.plugins.xsettings" does not seem to have any effect...only Psi reflects that.

Comment 10 Martin Stransky 2013-04-18 11:28:50 UTC
Please reopen if you have the requested data.

Comment 11 Chris Bainbridge 2013-05-28 14:50:39 UTC
This should be fixed upstream in Firefox 22 https://bugzilla.mozilla.org/show_bug.cgi?id=691661

Comment 12 Toon Verstraelen 2013-05-28 21:11:05 UTC
I just tested firefox 22 (the mozilla binary distribution). It also uses grayscale rendering, no matter what the settings in "org.gnome.settings-daemon.plugins.xsettings" are. As opposed to comment 9, other programs adhere to these settings.

wrt comment 9, What is Psi?

wrt comment 6, I running fedora 18. This is may graphics card:

00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller])
	Subsystem: Micro-Star International Co., Ltd. Device 7635
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 41
	Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at cc00 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915

No special video drivers were installed. I have a Dell UltrSharp screen with bgr order. The screen resolution is 1280x1024. I have no special font settings or dpi.

Comment 13 Jan Horak 2013-05-29 12:06:11 UTC
Try to disable Preferences/Advanced/General/Browsing/Use hardware acceleration when available. Then restart. This could be related to your GPU.

Comment 14 Toon Verstraelen 2013-05-30 19:57:35 UTC
Just tried disabling hardware acceleration. Still no luck. The results remain the same:

- The firefox browser that ships with fedora ignores the "rgba-order" setting and always uses "rgb" for this option when "antialiasing" is set to "rgba". 

- Firefox 22, as downloaded from mozilla.org, also ignores the "antialiasing" setting and always uses "grayscale".

Comment 15 Fedora End Of Life 2013-12-21 15:23:00 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2014-02-05 23:02:56 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 17 Jan Kurik 2015-07-15 14:51:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 18 Fedora End Of Life 2016-11-24 10:56:21 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 19 Fedora End Of Life 2016-12-20 12:35:13 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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