Closed Bug 635655 Opened 13 years ago Closed 13 years ago

Images in all browser toolbars display with black borders

Categories

(Core :: Graphics, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 635463

People

(Reporter: arbalan.in, Unassigned)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
Build Identifier: Firefox 4.0b12pre (2011-02-20)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b12pre) Gecko/20110220 Firefox/4.0b12pre

Distorted looks to the toolbars with black borders appearing I suppose against the toolbar images, and some distorted images too. Problem started after upgrading from 4.0b11 to 4.0b12pre.
However, the page contents render fine.

Reproducible: Always

Steps to Reproduce:
1. Open firefox 4.0b12pre

Actual Results:  
1. Black borders shown around images in the toolbar, address bar and status bar
2. Images in the tabbed browser bar show problems around the edges

Expected Results:  
Proper images in the toolbars as was there in 4.0b11

1. Had noticed on first upgrade to 4.0b12pre. A prior version though (2011-02-17 or 2011-02-18).
2. Tried restarting with add-ons disabled but it doesn't help.
3. The following appears on the about:support page. Not sure if it's relevant though -
Direct2D - EnabledBlocked on your graphics driver. Try updating your graphics driver to version 10.6 or newer.
You seem to be using a 64Bit Firefox Build (yet unsupported) and moreover forced enabled D2D Usage.

* try updating your Drivers if you're not using a Legacy ATI Card.
* try testing against a 32-Bit Build
* verify that setting gfx.direct2d.force-enabled to "false" fixes your Issue
Component: Toolbars → Graphics
Product: Firefox → Core
QA Contact: toolbars → thebes
Whiteboard: dupeme
Version: unspecified → Trunk
64-bit Firefox build was indeed in use.

1. As suggested, 32-bit Firefox was installed and that didn't show up the problem.
2. The gfx.direct2d.force-enabled was set to false (default value). Interestingly, once I toggled it to true, the problem resolved itself.
gfx.direct2d.force-enabled, when set to false gives me the problem as illustrated in the screenshot attached earlier.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Whiteboard: dupeme
Clipboard fail, correct bug this time.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: