Re: [csswg-drafts] [css-anchor-position-1] inset-inline-start: anchor(start) is confusing (#13734)

iiuc, a logical `inset` and a logical `anchor()` inset, for the same anchoring element, currently have the potential to resolve against different writing modes? a containing block could be `ltr` and the element could be `rtl`, at which point `inset-inline-start` for example would each resolve to something else depending if it's anchor `inset` or position `inset`? i suppose that makes sense… but is quite a potential gotcha. 

while the mentioned `self-start/self-end` could resolve some scenarios, there's others that need `calc()` and they can't quite tap into that beneficial edge case handling can they? not sure most web developers are going to be able to juggle distinguishing their containing block language modes vs their element language modes, aligning anchor inset to the element (target of the anchor) writing mode makes the most sense to me (at least right now in my current understanding).

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


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

Received on Friday, 27 March 2026 17:15:46 UTC