Open
Bug 967074
Opened 11 years ago
Updated 8 months ago
CSS repeating-linear-gradient rendering bug
Categories
(Core :: Graphics: WebRender, defect)
Core
Graphics: WebRender
Tracking
()
NEW
People
(Reporter: 7raivis, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(6 files, 1 obsolete file)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.102 Safari/537.36
Expected results:
CSS3 repeating-linear-gradient rendering bug, the stops should repeat every 3 pixels.
Also the visual appearance diffs on any browser.
Test cases:
http://jsfiddle.net/laukstein/K6XVw/2/ fine on IE11
http://jsfiddle.net/laukstein/K6XVw/14/ fine on Chrome 32, Safari 5.1.7
Related issues
https://code.google.com/p/chromium/issues/detail?id=155812
https://code.google.com/p/chromium/issues/detail?id=314383
I disagree with https://bugzilla.mozilla.org/show_bug.cgi?id=644444#c23 that Firefox rendering is the must correct.
1. Firefox has "transparency" bug like earlier had with CSS "border-color" - compare the visual appearance of http://jsfiddle.net/laukstein/K6XVw/15/ and http://jsfiddle.net/laukstein/K6XVw/2/. http://jsfiddle.net/laukstein/K6XVw/2/ must be as excatly http://jsfiddle.net/laukstein/K6XVw/15/.
2. Check http://jsfiddle.net/laukstein/K6XVw/17/ and http://jsfiddle.net/laukstein/K6XVw/15/ - they must return visualy accurately same result, but doesn't.
Updated•11 years ago
|
Component: Untriaged → Layout: View Rendering
Product: Firefox → Core
Comment 3•11 years ago
|
||
It looks different in every browser so I'll confirm this bug as NEW for now, though I'm not sure what the correct implementation would be.
dbaron, what do you think?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(dbaron)
Testcases should *always* be attached to bugs so we can have a conversation about them that will make sense in the future (in case the URLs referenced change or disappear).
I'm seeing rather different results from the screenshot on Linux. Either way, this is a Graphics bug... though I'm not sure exactly how cross-platform these results should be *expected* to be. I don't think any relevant specifications describe the pixel-rounding rules needed to get interoperable behavior here, and I'm not sure if platform APIs are powerful enough to give us that level of consistency with good performance at the same time.
Component: Layout: View Rendering → Graphics
Flags: needinfo?(dbaron)
trunk from a few days ago, about:support says:
Graphics
Adapter Description Tungsten Graphics, Inc -- Mesa DRI Intel(R) Sandybridge Mobile
Device ID Mesa DRI Intel(R) Sandybridge Mobile
Driver Version 3.0 Mesa 8.0.4
GPU Accelerated Windows 2/2 OpenGL (OMTC)
Vendor ID Tungsten Graphics, Inc
WebGL Renderer Tungsten Graphics, Inc -- Mesa DRI Intel(R) Sandybridge Mobile
windowLayerManagerRemote true
AzureCanvasBackend cairo
AzureContentBackend cairo
AzureFallbackCanvasBackend none
AzureSkiaAccelerated 0
And the Linux behavior looks the same, to my eyes anyway, if I drop the layers.acceleration.force-enabled pref and have about:support showing:
Graphics
Adapter Description Tungsten Graphics, Inc -- Mesa DRI Intel(R) Sandybridge Mobile
Device ID Mesa DRI Intel(R) Sandybridge Mobile
Driver Version 3.0 Mesa 8.0.4
GPU Accelerated Windows 0/1 Basic
Vendor ID Tungsten Graphics, Inc
WebGL Renderer Tungsten Graphics, Inc -- Mesa DRI Intel(R) Sandybridge Mobile
windowLayerManagerRemote false
AzureCanvasBackend cairo
AzureContentBackend cairo
AzureFallbackCanvasBackend none
AzureSkiaAccelerated 0
Updated•2 years ago
|
Severity: normal → S3
Comment 9•2 years ago
|
||
I think the second test case looks the same in Firefox, Safari, and Chromium now. The first test case still exposes some subtle differences.
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
Updated•2 years ago
|
Severity: S3 → --
Component: Graphics → Graphics: WebRender
Version: 30 Branch → unspecified
Updated•9 months ago
|
Attachment #9381331 -
Attachment is obsolete: true
Updated•8 months ago
|
Blocks: wr-gradients
You need to log in
before you can comment on or make changes to this bug.
Description
•