Re: [csswg-drafts] [css-anchor-position-1] Can we clarify the `inset-area` syntax? It can be confusing to read and reason about. (#9862)

Random thought: what if we give a name to all possible combinations that make sense. There are not many of them.

**Horizontal popups:**
> `above` (top, all), 
> `above-only` (top, center), 
> `above-and-before` (top, left+center), `above-and-before-only` (top, left), 
> `above-and-after` (top,center+right), `above-and-after-only` (top, right). 
> 
> Ditto with `below` as a prefix for the bottom row.

**Vertical popups:**
> `before` (all, left), 
> `before-only` (center, left), 
> `before-and-above` (top+center, left), 
> `before-and-above-only` (top, left), `before-and-below` (center+bottom, left), 
> `before-and-below-only` (bottom, left). 
> 
> Ditto with `after` as a prefix for the right column.

**Dialogs:**
For popus that cover the entire anchor, I suspect we can also add 
> `over` for (top+center+bottom, left+center+right) and 
> `over-only` (center, center).

All the other options look rare to me, and could be achieved with a less intuitive syntax.

Some cells have two names with this proposal (e.g. `above-and-after-only` and `after-and-above-only`) but maybe another naming scheme could avoid this (but maybe it's ok though, as they have slightly different semantics).

I can imagine `stritctly` being an appealing alternative to `only` (but it's a bit longer to type, and usually happens as first word in English, while `only` is allowed on both sides, but this is a detail).

-- 
GitHub Notification of comment by FremyCompany
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9862#issuecomment-1942155545 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 13 February 2024 18:30:07 UTC