Adds two CSS features. The 'clip' value results in a box’s content being clipped to the box's overflow clip edge. In addition, no scrolling interface is provided, and the content can not be scrolled by the user or programmatically. The overflow-clip-margin property enables specifying how far outside the bounds an element is allowed to paint before being clipped.
I'm not aware of any risks other than not being fully approved by W3C.
Not aware of any.
Not aware of any.
Not aware of any.
Only support needed is to surface the new value and property.
Adds two CSS features. The 'clip' value results in a box’s content being clipped to the box's overflow clip edge. In addition, no scrolling interface is provided, and the content can not be scrolled by the user or programmatically. The overflow-clip-margin property enables specifying how far outside the bounds an element is allowed to paint before being clipped.
I'm not aware of any risks other than not being fully approved by W3C.
Not aware of any.
Not aware of any.
Not aware of any.
Only support needed is to surface the new value and property.
On 01/12/2020 17:35, 'Scott Violet' via blink-dev wrote:
> Explainer
>
>
> https://drafts.csswg.org/css-overflow-3/#valdef-overflow-clip
> <https://drafts.csswg.org/css-overflow-3/#valdef-overflow-clip>
This is not an explainer, an explainer should include a summary of the
feature and use cases that it covers.
> Summary
>
> Adds two CSS features. The 'clip' value results in a box’s content being
> clipped to the box's overflow clip edge. In addition, no scrolling
> interface is provided, and the content can not be scrolled by the user
> or programmatically. The overflow-clip-margin property enables
> specifying how far outside the bounds an element is allowed to paint
> before being clipped.
These look like 2 different but related features. What's the maturity
status in the spec regarding them? I see a few issues open on the CSSWG
about both of them, are them important? Should we try to clarify them
and agree on a common behavior before shipping?
> Interoperability and Compatibility
>
> I'm not aware of any risks other than not being fully approved by W3C.
One interop risk would be if other browsers don't support this. How that
would affect pages using these properties?
> Gecko: Shipped/Shipping
> (https://groups.google.com/g/mozilla.dev.platform/c/7oQm8PC0aU0
> <https://groups.google.com/g/mozilla.dev.platform/c/7oQm8PC0aU0>) I
> marked this shipping, but Firefox is in the intent-to-ship phase.
Gecko shipped "overflow: clip" in version 81:
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/81#CSS
But they haven't implemented "overflow-clip-margin" yet:
https://drafts.csswg.org/css-overflow-3/#valdef-overflow-clip
> WebKit: No signal
Have we asked for WebKit signals https://bit.ly/blink-signals ?
I know there has been some work regarding overflow in WebKit recently,
so it'd be nice to check what they think about these features.
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>?
>
> No
Why not?
Note that "overflow-clip-margin" interacts with css-contain, so that
kind of things should be tested too.
Bye,
Rego
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKARY_niBvimC0SsmhF_Q2ROnx%3D6R%2BJ_ZPKcXGWxvtHPqu5u5g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9u1H_52F3FUgP2W%3DRb9Bjf5fqownwzRa1jhGs3on8KQA%40mail.gmail.com.
A few comments here.
I couldn't find tests for the "<visual-box>" part of the
overflow-clip-margin syntax:
https://drafts.csswg.org/css-overflow/#overflow-clip-margin
Actually I'm not sure if the implementation supports that or not.
Could you clarify that?
I'd suggest also adding parsing tests for this property.
The runtime flag is still marked as "test" in
runtime_enabled_features.json5. I believe the usual thing is to have it
marked as "experimental" for a while before shipping it.
That means that we cannot check the status of tests interop in wpt.fyi
for example: https://wpt.fyi/results/css/css-overflow
Also some tests are passing in all browsers even without support for the
overflow-clip-margin property yet (also some are only passing on WebKit
I guess due to the overlay scrollbars).
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/027de420-a9f3-2b60-68d7-fdf6496499c6%40igalia.com.