Tab Atkins Jr.

Screenshots to illustrate the problem, based on the example in my previous comment. The popup is using `position-area: bottom span-right;` to position itself below the button that invokes it. It's...

Okay, first draft of the new spec text committed. It was a larger change than I thought it would be at first, but I think this captures the behavior we...

> What's the definition of first laid out? With container queries and scroll timelines there may be multiple passes where a box flips between being rendered and not in different...

Nope, the spec explicitly prevents that from happening; see [step 2.1 of "determine fallback styles"](https://drafts.csswg.org/css-anchor-position/#determine-position-fallback-styles), where we check if the styles are the currently-used ones and skip over them.

Sorry for the delay, @mstensho . Yeah, Blink appears to be violating the spec, tho that might be a reasonable thing to do. I put in the restriction of "only...

> And if there's non-default position-try-order, we have to always try them all anyway, regardless of how the spec is interpreted (cannot wait for overflow then). I don't understand what...

We already have a resolution for it: The comment you link to is just me explaining the details of how I implemented the resolution.

For clarity, since I had to poke around in the examples to understand the pictures: * in each pair, the first is an *unstyled* scrollbar, the second is given a...

I do agree that simply using the specified 'scrollbar-color' directly in all locations and states is a usability regression; you lose the hover color-change, and the arrow color-change indicating which...

Hm, this definitely solves the round-trip (setting a longhand to itself) and cssText issues, but still doesn't let you reserialize the shorthand when one of the longhands is modified. If...