mask-image-interpolation CSS-transition failed
Categories
(Core :: Layout, defect, P3)
Tracking
()
People
(Reporter: haozhes, Unassigned)
Details
Attachments
(2 files, 1 obsolete file)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
Steps to reproduce:
Create a local server under wpt, and open localhost:8000/ + path to the test
Run the attached test with Firefox nightly build.
Actual results:
See the attached image.
Expected results:
Pass all the test
The spec is here: https://drafts.fxtf.org/css-masking-1/#the-mask-image
Comment 4•5 years ago
|
||
Hi ,
I wasn't able to reproduce the bug but I've chosen a component for this bug in hope that someone with more expertise may look at it. We'll await their answer. If you consider that there's another component that's more proper for this case you may change it.
Regards, Flor.
Comment 5•5 years ago
|
||
Boris: Do you know if we are supposed to support mask-image transitions?
Comment 6•5 years ago
•
|
||
(In reply to Sean Voisen (:svoisen) from comment #5)
Boris: Do you know if we are supposed to support mask-image transitions?
It's discrete animation (i.e. flip at 50%), based on the spec definition. So I suspect we should use test_no_interpolation()
in wpt.
[css-transitions] defines transitionable: When comparing the before-change style and after-change style for a given property, the property values are transitionable if they have an animation type that is neither not animatable nor discrete.
In other words, mask-image
is a non-transitionable property (i.e. its value should be flipped immediately after specifying a new one). That's why we don't pass the incorrect wpt.
Comment 7•5 years ago
|
||
A similar case is border-image-source
, whose animation type is also discrete. We use test_no_interpolation
in wpt [1] and we pass all.
Comment 8•5 years ago
|
||
Just notice there is a related spec issue: https://github.com/w3c/csswg-drafts/issues/4441
Comment 9•5 years ago
|
||
I imagine at some point that spec will be updated to interpolate using computed value so that <image>
values get cross-fade()
interpolation (which we don't support per bug 546052)--although there are still a few spec issues surrounding that.
Updated•2 years ago
|
Description
•