Rendering error using border:radius, border and background:linear-gradient

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
5 years ago
3 years ago

People

(Reporter: mozilla, Unassigned)

Tracking

26 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

5 years ago
Created attachment 8365609 [details]
Image1.jpg

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

Steps to reproduce:

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>test</title>
<style type="text/css">
li {list-style: none inside;margin:0; padding:0}

ul a {
    display: block;
    width: 100px;
    color: #FFFFFF;

    height: 22px;
    line-height:22px;

    text-align:center;
    border:2px outset #FFF;
    border-radius:14px;

    background: #FF0000;

    background: -moz-linear-gradient(top,  #EF5263,  #EA1D25);

    background: linear-gradient(#EF5263, #EA1D25);
}
</style>
</head>
<body>
<ul><li><a href="#">About</a></li></ul>
</body>
</html>


Actual results:

The above html/css exposes an issue that appears to have been introduced in Firefox 26. The issue does not appear in Firefox 25.01. It does not happen in Chrome, Opera, Safari or IE11.

The bottom left and top right corners have a triangle shape over the them, rather than the expected radiused border.


Expected results:

The borders should appear with the correct radius.
I don't see this on Linux trunk; seems likely to be Windows only, though probably worth checking.
Component: Layout: View Rendering → Graphics
qawanted to:
 * check whether this is a duplicate
 * if it's not, see if it's cross platform or Windows only, and whether it's still reproduces on trunk
 * if it's still on trunk, find a regression window for when it started
Keywords: qawanted, regressionwindow-wanted
No bug that I can see on mac either.
(Reporter)

Comment 5

5 years ago
My Machine is win7 pro 64 bit. I just tried the test case on XP 32 bit machine, with FF 26 and there is no issue.

It may be that this is a Win7 or 64 bit issue.

Comment 6

5 years ago
I can't reproduce with either trunk or Firefox 26.0 on my Windows 7 64-bit installation.
User agents: 
[1] Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 
[2] Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:29.0) Gecko/20100101 Firefox/29.0
[3] Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
[4] Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0

I was unable to reproduce this issue on two different machines running Windows 7 64-bit using the reporter's testcase with: 
- Fx 26.0 (Build ID: 20131205075310) [1]
- latest Nightly (Build ID: 20140128031716) [2] 
- latest Aurora (Build ID: 20140128004001) [3]
- latest Beta (Build ID: 20140123185438)[4] 

JeRo, have you tried:
1. reproducing this issue on the latest Nightly?
* latest Nightly: http://mzl.la/19YPNvL
2. reproducing this issue on a clean profile?
* how-to: http://mzl.la/1bv7IFx
3. reproducing this issue in Safe Mode?
* how-to: http://mzl.la/1b0uwA6
4. reproducing this issue after resetting Firefox?
* how-to: http://mzl.la/18ceOCK
Flags: needinfo?(mozilla)
Keywords: qawanted, regressionwindow-wanted
(Reporter)

Comment 8

5 years ago
Issue persists on a clean profile

Issue persists after a reset

Issue does NOT persist in safe mode

Incidentally, I tried disabling every addon and extension, problem persisted.

I have yet to try the nightly build.
The problem might be with the specific graphics card or drivers. You could try disabling hardware acceleration.
(In reply to Timothy Nikkel (:tn) from comment #9)
> The problem might be with the specific graphics card or drivers. You could
> try disabling hardware acceleration.

Hi Timothy and thank you for assisting. 

(In reply to JeRo from comment #8)
> Issue persists on a clean profile
> 
> Issue persists after a reset
> 
> Issue does NOT persist in safe mode
> 
> Incidentally, I tried disabling every addon and extension, problem persisted.
> 
> I have yet to try the nightly build.

JeRo, since Firefox's Safe Mode also disables hardware acceleration, the problem might be indeed caused by your specific graphics card or by the installed driver. Could you please provide the name of your display adapter and also the driver version you have installed for it?

You can see that by accessing the about:support page > "Graphics" section > "Adapter Description" and "Driver Version".
(Reporter)

Comment 11

5 years ago
I have dual graphics cards:

Intel G41 Express Chipset (built in to motherboard)
Driver version 8.15.10.2302 Date 11/02/11 (Intel Corporation)

ATI Radeon HD 5450
Driver version 2.821.0.0 Date 26/01/11 (ATI Technologies Inc)

Since doing a fresh install a couple of weeks ago, I have had the odd error with the graphics drivers crashing and needing to restart. I installed updated drivers from Windows Update for both cards, and driver crashes have stopped, although the rendering issue in FF persists.

The option to disable hardware acceleration (troubleshoot->change settings) is greyed out on both adapters, so I don't think I can disable hardware acceleration.


Adapter Description	Intel(R) G41 Express Chipset
Adapter Description (GPU #2)	ATI Radeon HD 5450
Adapter Drivers	igdumd64 igd10umd64 igdumdx32 igd10umd32
Adapter Drivers (GPU #2)	aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM	Unknown
Adapter RAM (GPU #2)	512
ClearType Parameters	DISPLAY1 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 0 Enhanced Contrast: 50 ] DISPLAY2 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ]
Device ID	0x2e32
Device ID (GPU #2)	0x68f9
Direct2D Enabled	true
DirectWrite Enabled	true (6.2.9200.16571)
Driver Date	2-11-2011
Driver Date (GPU #2)	1-26-2011
Driver Version	8.15.10.2302
Driver Version (GPU #2)	8.821.0.0
GPU #2 Active	false
GPU Accelerated Windows	2/2 Direct3D 10
Vendor ID	0x8086
Vendor ID (GPU #2)	0x1002
WebGL Renderer	Google Inc. -- ANGLE (Intel(R) G41 Express Chipset Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote	false
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
(Reporter)

Comment 12

5 years ago
Issue persists with the Nightly build (I assume I just unzip the file and run it - no installer)
(Reporter)

Comment 13

5 years ago
Running *Windows* in safe mode fixes the issue.
Flags: needinfo?(mozilla)
(In reply to JeRo from comment #12)
> Issue persists with the Nightly build (I assume I just unzip the file and
> run it - no installer)
That's right.

(In reply to JeRo from comment #13)
> Running *Windows* in safe mode fixes the issue.
I see, so running Firefox in Safe Mode or running Windows in Safe Mode fixes this issue, both modes affect the video card's involvement.

(In reply to JeRo from comment #11)
> The option to disable hardware acceleration (troubleshoot->change settings) is greyed out on both 
> adapters, so I don't think I can disable hardware acceleration.
Please let me know if the following instructions work instead: http://mzl.la/Meeaur.
(Reporter)

Comment 15

5 years ago
I wasn't aware there was a hardware acceleration option in Firefox itself D'oh!

Turning it off and restarting FF DOES fix the issue.

Thanks to everyone for their assistance. 

If there are any fixes, please let me know and I will gladly test.
(In reply to JeRo from comment #15)
> I wasn't aware there was a hardware acceleration option in Firefox itself
> D'oh!
> 
> Turning it off and restarting FF DOES fix the issue.
> 
> Thanks to everyone for their assistance. 
> 
> If there are any fixes, please let me know and I will gladly test.

You're very welcome. I strongly recommend also checking for driver updates using either Windows Update (http://mzl.la/MtFjdG) or AMD's support page (http://mzl.la/1jHYnSR). Could you please confirm whether you're using the latest driver or not?

Updated

3 years ago
Duplicate of this bug: 1191505
You need to log in before you can comment on or make changes to this bug.