Closed Bug 851764 Opened 13 years ago Closed 5 years ago

Artifact on Back button when moving cursor.

Categories

(Core :: Graphics, defect)

All
Windows 8
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ryan.johnk, Unassigned)

References

Details

Attachments

(2 files)

Attached image artifact2_ff20beta.png
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0 Build ID: 20130313170052 Steps to reproduce: Open Firefox beta 20 Actual results: Back button has artifacts when mouse cursor moves over it or near it. Expected results: Back button is rendered cleanly on the screen.
Attached image artifact_ff20beta
Does it reproduce with Clean profile or using Safe mode? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles This should be moved to Toolbars or General component.
Flags: needinfo?(johnkfamily)
I could reproduce this issue on my Windows 7 32bit, on Firefox 20 beta 7 and on the 03/26 Aurora and Nightly.
Status: UNCONFIRMED → NEW
Component: Untriaged → Toolbars
Ever confirmed: true
Flags: needinfo?(johnkfamily)
Hardware: x86_64 → All
If you set `gfx.content.azure.enabled` to false in about:config, does this fix things?
Flags: needinfo?(johnkfamily)
I have set the flag to false, and there is no artifacts or other issues.
Flags: needinfo?(johnkfamily)
Doing so also makes the address bar pull-down black, (appearing when you begin to type a url or search term, for example). I don't know if that's a side effect of setting the gfx string to false though.
Also, this bug does not appear when I set the toolbar to use small icons.
> Doing so also makes the address bar pull-down black... is this happen if set `gfx.direct2d.disabled` to true?
I can reproduce on Mozilla/5.0 (Windows NT 6.1; rv:23.0) Gecko/20130415 Firefox/23.0 my graphics section: Graphics Adapter Description Mobile Intel(R) 4 Series Express Chipset Family Adapter Drivers igdumdx32 igd10umd32 Adapter RAM Unknown ClearType Parameters Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 100 Device ID 0x2a42 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.16492) Driver Date 10-13-2011 Driver Version 8.15.10.2555 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 10 Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Mobile Intel(R) 4 Series Express Chipset Family) AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo
Component: Toolbars → Graphics
Product: Firefox → Core
Version: 20 Branch → Trunk
I've switched content.azure.enabled to false and direct2d.disabled to true. There are no artifact or other screen draw bugs.
(In reply to johnkfamily from comment #10) > I've switched content.azure.enabled to false and direct2d.disabled to true. > > There are no artifact or other screen draw bugs. Thank you for testing this. :)
Seems closely related to bug 849517, and maybe also related to bug 894542 and bug 901336, which all seem to be graphical issues with rounded borders with Intel graphics with Device ID 0x24a2.
What does the Graphics section of your about:support say?
Flags: needinfo?(ioana.budnar)
And what does *your* Graphics section of about:support say?
Flags: needinfo?(johnkfamily)
(In reply to David Baron [:dbaron] (don't cc:, use needinfo? instead) from comment #13) > What does the Graphics section of your about:support say? I have changed my machine a while ago, so I can't get you that information anymore. All I know about the old machine's graphics is that it had a Intel G41 Express Chipset. I now have Intel HD 4000 graphics and I can't reproduce the issue with it (tried on Firefox 20 and 25).
Flags: needinfo?(ioana.budnar)
I'm only seeing this intermittently (so i'm not entirely sure this is the same issue), but i've noticed it again with the current Nightly. Graphics -------- Adapter Description: Intel(R) HD Graphics Family Adapter Description (GPU #2): NVIDIA NVS 4200M Adapter Drivers: igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32 Adapter Drivers (GPU #2): nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Adapter RAM: Unknown Adapter RAM (GPU #2): 1024 Device ID: 0x0126 Device ID (GPU #2): 0x1057 Direct2D Enabled: true DirectWrite Enabled: true (6.2.9200.16571) Driver Date: 3-6-2011 Driver Date (GPU #2): 5-25-2011 Driver Version: 8.15.10.2321 Driver Version (GPU #2): 8.17.12.6871 GPU #2 Active: false GPU Accelerated Windows: 1/1 Direct3D 10 Vendor ID: 0x8086 Vendor ID (GPU #2): 0x10de WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote: false AzureCanvasBackend: direct2d AzureContentBackend: direct2d AzureFallbackCanvasBackend: cairo AzureSkiaAccelerated: 0
Georg, your GPU drivers are pretty old. Is it possible for you to update them and test?
(In reply to David Baron [:dbaron] (don't cc:, use needinfo? instead) from comment #12) > Seems closely related to bug 849517, and maybe also related to bug 894542 > and bug 901336, which all seem to be graphical issues with rounded borders > with Intel graphics with Device ID 0x24a2. Setting qawanted to ask if we have a system like this available?
Keywords: qawanted
We don't have such a system. Anthony, can anyone on your side help here?
(In reply to Milan Sreckovic [:milan] from comment #18) > Intel graphics with Device ID 0x24a2. What GPU chipset does this hex code correlate to?
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #20) > What GPU chipset does this hex code correlate to? Bug 849517 comment 1 has some details on this.
(In reply to Ioana Budnar, QA [:ioana] from comment #21) > (In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #20) > > What GPU chipset does this hex code correlate to? > > Bug 849517 comment 1 has some details on this. That only tells me "Intel Series 4..." which covers an entire family of chipsets. I need to know specifically which GPU in the "Series 4" family the hex code 0x24a2 correlates to.
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(ryan.johnk)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: