947477 - Location Bar autocomplete choice drop down black

Status: RESOLVED INCOMPLETE

(Core :: Graphics, defect)

Description

[Jim Taylor]

Attachment: screenshot.jpg

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 (Beta/Release)
Build ID: 20131203183810

Steps to reproduce:

Settings:
Autocomplete from your browsing history as you type.
Automatically prefill the best match.
Show list of matching results.

Start typing a url into the location bar


Actual results:

The drop down that should show the list of matching results is Black (see screen shot attached)


Expected results:

Drop down should show a list of matching results.

Comment 1

[Jim Taylor]

I have discovered that the problem only occurs when gfx.content.azure.enabled=false in about:config.
If gfx.content.azure.enabled=true the autocomplete results drop down functions correctly.

I believe that gfx.content.azure.enabled=true is the default, however, changing it to false was a workaround for the bug 812694 display rendering problems caused by Microsoft's platform update so I expect quite a few people have changed it to false.

Comment 2

[therube]

Confirmed.

Comment 3

[therube]

FF 25.0 is likewise affected (haven't put in 25.0.1).

It is not only the "dropdown", but other things too, like when hoovering the screenshot.jpg link in this bug.

Comment 4

[therube]

SeaMonkey 2.25a1 is not affected, so you would think it would be fixed in ... well along side the fix for Bug 812695 - [D2D] Text Rendering Issues on Windows 7 with Platform Update KB2670838 (MSIE 10 Prerequisite) or on Windows 8.1 ?

But that fix should land in FF 26, which would seem to mean that SeaMonkey 2.23beta1 should not be affected, yet it is?

So if I'm reading it right, then maybe there is something missing on our end?

Comment 5

[therube]

FF 26.0 candidate build 2 is also affected.
Go figure.

Comment 6

[therube]

The probably belongs in Core, Graphics ?

Comment 7

[Jim Taylor]

(In reply to Jim Taylor from comment #1)
> I have discovered that the problem only occurs when
> gfx.content.azure.enabled=false in about:config.
> If gfx.content.azure.enabled=true the autocomplete results drop down
> functions correctly.
> 
> I believe that gfx.content.azure.enabled=true is the default, however,
> changing it to false was a workaround for the bug xxxxxx display rendering
> problems caused by Microsoft's platform update so I expect quite a few
> people have changed it to false.

Bug number for display problem is wrong in comment 1 it should be bug 812695.

Also at least for me 2.23b1 contains the hidden pref layout.paint_rects_separately for bug 934860 which when created and set to true fixes the bug 812695 display problem allowing gfx.content.azure.enabled to be changed back to true which corrects this problem.  So that's the way I'm running at the moment, but I can change back to test or provide more information if needed.

Comment 8

[Jens Hatlak (:InvisibleSmiley)]

(In reply to therube from comment #6)
> The probably belongs in Core, Graphics ?

Since you could reproduce with FF, yes, definitely. This bug has a much higher chance of getting noticed and fixed over there.

Comment 9

[Jim Taylor]

I have changed this bug to core-graphics as suggested.  I wasn't sure of the version as I don't have Firefox installed so used 26 branch as I think that is the common code for SeaMonkey 2.23b1.

Comment 10

[Martin]

I'm using FF 26.0 and get this issue. I have gfx.content.azure.enabled set to false because of the font rendering bug(In reply to Jim Taylor from comment #7)
> (In reply to Jim Taylor from comment #1)
> > I have discovered that the problem only occurs when
> > gfx.content.azure.enabled=false in about:config.
> > If gfx.content.azure.enabled=true the autocomplete results drop down
> > functions correctly.
> > 
> > I believe that gfx.content.azure.enabled=true is the default, however,
> > changing it to false was a workaround for the bug xxxxxx display rendering
> > problems caused by Microsoft's platform update so I expect quite a few
> > people have changed it to false.
> 
> Bug number for display problem is wrong in comment 1 it should be bug 812695.
> 
> Also at least for me 2.23b1 contains the hidden pref
> layout.paint_rects_separately for bug 934860 which when created and set to
> true fixes the bug 812695 display problem allowing gfx.content.azure.enabled
> to be changed back to true which corrects this problem.  So that's the way
> I'm running at the moment, but I can change back to test or provide more
> information if needed.

I'm using FF 26.0 and had to set;
> gfx.content.azure.enabled=false
to fix bug 812694 but now I get the black box on any autocomplete in the browser. Tried setting gfx.content.azure.enabled=true but instantly my font issue was back and I was still seeing black boxes in place of autocomplete in the browser. Haven't restarted the browser yet as the setting change was instantly noticable, not sure if maybe restart is needed for the autocomplete.

What is the latest on this?

Comment 11

[Martin]

(In reply to lankymart from comment #10)
> I'm using FF 26.0 and had to set;
> > gfx.content.azure.enabled=false
> to fix bug xxxxxx but now I get the black box on any autocomplete in the
> browser. Tried setting gfx.content.azure.enabled=true but instantly my font
> issue was back and I was still seeing black boxes in place of autocomplete
> in the browser. Haven't restarted the browser yet as the setting change was
> instantly noticable, not sure if maybe restart is needed for the
> autocomplete.
Sorry posted wrong bug should be bug 812695

Comment 12

[Martin]

Found setting
>gfx.content.azure.backends=cairo
>gfx.content.azure.enabled=true
fixes both the font rendering and the black boxes appearing for autocomplete and context menus.