Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
"shape-outside", "cursor" and "-webkit-mask-box-image".
Should we consider the `mask-image`?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
"shape-outside", "cursor" and "-webkit-mask-box-image".
Should we consider the `mask-image`?
The mask-image property uses the CSSToStykeMap::MapFillImage codepath, which already applies the ResolveGradient function, introduced in the previous CL #6676851.
Anyway, I'll add new WPT test cases in this CL.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
"shape-outside", "cursor" and "-webkit-mask-box-image".
Javier FernandezShould we consider the `mask-image`?
The mask-image property uses the CSSToStykeMap::MapFillImage codepath, which already applies the ResolveGradient function, introduced in the previous CL #6676851.
Anyway, I'll add new WPT test cases in this CL.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
state.GetStyleImage(CSSPropertyID::kBorderImageSource, resolved_value));
Should `GetStyleImage()` ultimately do this instead?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thanks for the review.
See my reply inline.
state.GetStyleImage(CSSPropertyID::kBorderImageSource, resolved_value));
Should `GetStyleImage()` ultimately do this instead?
Good question ! That was precisely the first version of my patch. However, given that there is a FIXME in that function suggesting that it will be eventually removed, I decided to avoid that approach.
Additionally, I thought that doing it explicitly for each css property would be clearer.
I could get back the original approach if you thing it's better. The patch would be simpler, indeed.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
"shape-outside", "cursor" and "-webkit-mask-box-image".
Javier FernandezShould we consider the `mask-image`?
一丝The mask-image property uses the CSSToStykeMap::MapFillImage codepath, which already applies the ResolveGradient function, introduced in the previous CL #6676851.
Anyway, I'll add new WPT test cases in this CL.
Nice!
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
state.GetStyleImage(CSSPropertyID::kBorderImageSource, resolved_value));
Javier FernandezShould `GetStyleImage()` ultimately do this instead?
Good question ! That was precisely the first version of my patch. However, given that there is a FIXME in that function suggesting that it will be eventually removed, I decided to avoid that approach.
Additionally, I thought that doing it explicitly for each css property would be clearer.
I could get back the original approach if you thing it's better. The patch would be simpler, indeed.
Yeah, I think it's better to do it in a single place. Just remove the FIXME; it's not sacred.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
state.GetStyleImage(CSSPropertyID::kBorderImageSource, resolved_value));
Javier FernandezShould `GetStyleImage()` ultimately do this instead?
Anders Hartvoll RuudGood question ! That was precisely the first version of my patch. However, given that there is a FIXME in that function suggesting that it will be eventually removed, I decided to avoid that approach.
Additionally, I thought that doing it explicitly for each css property would be clearer.
I could get back the original approach if you thing it's better. The patch would be simpler, indeed.
Yeah, I think it's better to do it in a single place. Just remove the FIXME; it's not sacred.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Apply the CSSGradientValue resolution to other properties
This change calls to the ResolveGradient function for several CSS
properties that accept CSSGRadientValues as <image> values. These
properties are "border-image-source", "list-style-image", "content",
"shape-outside", "cursor" and "-webkit-mask-box-image".
It's worth mentioning that the "cursor" property doesn't support <image>
values yet as <cursor-image>, although it's specified [1], just <url> or
<url-set>. That's why the new WPT tests have failure expectations for
now.
The failures expectations of the shape-outside test cases are related to
the issue #40468636 or a subset of it. The problem is that chrome
serializes 50% as center, when it should use a <LengthPercentage> as
computed value.
[1] https://drafts.csswg.org/css-ui-4/#typedef-cursor-cursor-image
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The WPT PR for this CL has been merged upstream! https://github.com/web-platform-tests/wpt/pull/54972
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |