Closed
Bug 970600
Opened 11 years ago
Closed 11 years ago
Enable background-blend-mode by default
Categories
(Core :: Web Painting, defect)
Tracking
()
VERIFIED
FIXED
mozilla30
Tracking | Status | |
---|---|---|
relnote-firefox | --- | 30+ |
People
(Reporter: olaru, Assigned: olaru)
References
(Depends on 1 open bug)
Details
(Keywords: dev-doc-complete, feature)
Attachments
(6 files, 3 obsolete files)
Enable the background-blend-mode CSS property be default in Release builds.
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8373667 -
Flags: review?(roc)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → olaru
Attachment #8373667 -
Attachment is patch: true
Attachment #8373667 -
Attachment mime type: message/rfc822 → text/plain
Comment on attachment 8373667 [details] [diff] [review] enable-background-blend-mode-by-default Review of attachment 8373667 [details] [diff] [review]: ----------------------------------------------------------------- Most of your patch removes trailing whitespace from all.js. Please do that in a separate patch :-)
Attachment #8373667 -
Flags: review?(roc) → review-
Assignee | ||
Comment 3•11 years ago
|
||
Sorry about that :) Should be better in this patch. I don't mind adding a patch that removes trailing whitespace later, but isn't that a bit disruptive for source control history?
Attachment #8373667 -
Attachment is obsolete: true
Attachment #8373933 -
Flags: review?(roc)
(In reply to Horia Iosif Olaru from comment #3) > I don't mind adding a patch that removes trailing whitespace later, but > isn't that a bit disruptive for source control history? We generally don't see that as a problem.
Attachment #8373933 -
Flags: review?(roc) → review+
Updated•11 years ago
|
Keywords: dev-doc-needed
Comment 5•11 years ago
|
||
try build: https://tbpl.mozilla.org/?tree=Try&rev=a3784a6acc0e
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 6•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/01fd47b5eb1d
Keywords: checkin-needed
Comment 7•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/01fd47b5eb1d
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Updated•11 years ago
|
relnote-firefox:
--- → ?
Comment 8•11 years ago
|
||
Just tested this in latest Nightly windows7 32 bit. In all the test the purple color is displayed. See attachment.
Comment 9•11 years ago
|
||
Comment 10•11 years ago
|
||
Attachment #8376310 -
Attachment is obsolete: true
Attachment #8376312 -
Attachment is obsolete: true
Assignee | ||
Comment 11•11 years ago
|
||
(In reply to Peter Kroon from comment #8) > Created attachment 8376310 [details] > screenshot.png > > Just tested this in latest Nightly windows7 32 bit. > In all the test the purple color is displayed. See attachment. There seems to be a rendering difference for gradients between Firefox and Chrome. The violet you are seeing happens when the gradient goes from a fully transparent color to a fully opaque one. The color is violet because the starting point is a fully transparent blue (0, 0, 255, 0). If the color components would be black (0, 0, 0, 0) you would see a grey that appears between the two gradient start points. I have not looked into which would be the correct behavior. I will attach a test and some screenshots.
Assignee | ||
Comment 12•11 years ago
|
||
Assignee | ||
Comment 13•11 years ago
|
||
Assignee | ||
Comment 14•11 years ago
|
||
Assignee | ||
Comment 15•11 years ago
|
||
An interesting observation is when interpolating from or to a transparent color - Firefox takes the color components of the transparent stop point into account - Chrome seems to take the color components of the non transparent stop point for both ends when interpolating (it looks like a gradient from (255, 0, 0, 0) to (255, 0, 0, 1))
Comment 16•11 years ago
|
||
(In reply to Horia Iosif Olaru from comment #15) > An interesting observation is when interpolating from or to a transparent > color > - Firefox takes the color components of the transparent stop point into > account > - Chrome seems to take the color components of the non transparent stop > point for both ends when interpolating (it looks like a gradient from (255, > 0, 0, 0) to (255, 0, 0, 1)) This is because the CSS WG defined that gradients should interpolate in premultiplied colorspace (see my objection over this here: http://w3cmemes.tumblr.com/post/34628700024/when-worf-says-transparent-he-means) Chrome is following the spec here and firefox is not.
Comment 17•11 years ago
|
||
(In reply to Rik Cabanier from comment #16) > (In reply to Horia Iosif Olaru from comment #15) > > An interesting observation is when interpolating from or to a transparent > > color > > - Firefox takes the color components of the transparent stop point into > > account > > - Chrome seems to take the color components of the non transparent stop > > point for both ends when interpolating (it looks like a gradient from (255, > > 0, 0, 0) to (255, 0, 0, 1)) > > This is because the CSS WG defined that gradients should interpolate in > premultiplied colorspace (see my objection over this here: > http://w3cmemes.tumblr.com/post/34628700024/when-worf-says-transparent-he- > means) > Chrome is following the spec here and firefox is not. Has this been reported yet?
Assignee | ||
Comment 18•11 years ago
|
||
(In reply to Peter Kroon from comment #17) > (In reply to Rik Cabanier from comment #16) > > (In reply to Horia Iosif Olaru from comment #15) > > > An interesting observation is when interpolating from or to a transparent > > > color > > > - Firefox takes the color components of the transparent stop point into > > > account > > > - Chrome seems to take the color components of the non transparent stop > > > point for both ends when interpolating (it looks like a gradient from (255, > > > 0, 0, 0) to (255, 0, 0, 1)) > > > > This is because the CSS WG defined that gradients should interpolate in > > premultiplied colorspace (see my objection over this here: > > http://w3cmemes.tumblr.com/post/34628700024/when-worf-says-transparent-he- > > means) > > Chrome is following the spec here and firefox is not. > > Has this been reported yet? Yes - this seems to be the exact same issue: https://bugzilla.mozilla.org/show_bug.cgi?id=591600
Updated•11 years ago
|
QA Contact: bogdan.maris
Updated•11 years ago
|
QA Contact: bogdan.maris → catalin.varga
Comment 19•11 years ago
|
||
I verified this bug using: Firefox 30 Build id: 20140228030206 Os Win 7, Ubuntu 12.04 x 32 and Mac Os 10.9 I've used the following test: http://html.adobe.com/webplatform/graphics/blendmodes/browser-support/?filter=background During the test I've noticed that most of the images were different and the difference extended on to the circles not just the background. My assumption is that due to the bug https://bugzilla.mozilla.org/show_bug.cgi?id=591600 the backround is changing and those changes in addition to the backround blending and rendering are changing the aspect of the circles. I've attached and example that shows the differences that I was talking about.
Comment 20•11 years ago
|
||
(In reply to Catalin Varga [QA][:VarCat] from comment #19) > Created attachment 8383724 [details] > picture > > I verified this bug using: > > Firefox 30 > Build id: 20140228030206 > Os Win 7, Ubuntu 12.04 x 32 and Mac Os 10.9 > > I've used the following test: > http://html.adobe.com/webplatform/graphics/blendmodes/browser-support/ > ?filter=background > > During the test I've noticed that most of the images were different and the > difference extended on to the circles not just the background. > My assumption is that due to the bug > https://bugzilla.mozilla.org/show_bug.cgi?id=591600 the backround is > changing and those changes in addition to the backround blending and > rendering are changing the aspect of the circles. I'm unsure if that's the case. The background has no alpha so it should make no difference is the gradient is premultiplied. > I've attached and example that shows the differences that I was talking > about. This looks more like a color management issue.
Comment 22•11 years ago
|
||
This is not a bug with blending. Notice how the gradient itself is rendered differently.
Comment 23•10 years ago
|
||
Doc updated (thanks to all those who helped): https://developer.mozilla.org/en-US/docs/Web/CSS/background-blend-mode https://developer.mozilla.org/en-US/docs/Web/CSS/blend-mode https://developer.mozilla.org/en-US/Firefox/Releases/30
Keywords: dev-doc-needed → dev-doc-complete
Comment 24•10 years ago
|
||
Marking this bug as Verified as the feature was released with Firefox 30.
Status: RESOLVED → VERIFIED
Depends on: 1234649
Updated•6 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•