Simon Fraser

Ah, I didn't know that Firefox implemented. WebKit is the laggard. Files using `waitForScrollendEventNoTimeout()` include these (possibly more): ``` css/css-scroll-snap/scroll-snap-nested-snap-area-layout-changed.tentative.html css/css-scroll-snap/smooth-anchor-scroll-in-snap-container.html css/css-scroll-snap/snap-fling-in-large-area.html css/css-scroll-snap/unrelated-gesture-scroll-during-snap.html ``` and many more use `runLayoutSnapSeletionVerificationTest` which...

We're so used to thinking about "permission prompts" in the web space that this API is confusingly named. Also, in the AI space, "prompt engineering" is a fairly specific thing....

https://github.com/w3c/largest-contentful-paint

I envisioned overscroll events being about rubber banding within a given scrollable area (sending scroll event with negative offsets is not very web-compatible). Using them to propagate information about scrolls...

Yes I think it could be clearer. What I would expect, for sequence of user scrolls and a rubber band, would be scroll scroll ... scroll overscroll ... overscroll scrollend...

I think the problem there is that different platforms will have different kinds of inputs that trigger overscroll, so the only thing you can accurately report is the overscroll pixel...

Filed as https://bugs.webkit.org/show_bug.cgi?id=298554 How can this content be accessed?

We think that `corner-shape` will be useful to allow for bevel, and superellipse (aka squircle), but we believe that more complex corner shapes are best handled with some future `border-shape`...

Maybe we need a Basic Shape that is a `compound-path(windRule, shape1, shape2, ...)` that takes two or more other Basic Shapes and combines them with the given wind rule?

This looks like a use case for `border-shape`.