- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Sep 2024 01:51:35 +0000
- To: public-css-archive@w3.org
> the main question here is whether, when changing from one position-type to another, you get weird unexpected interference from other position-* if you fail to reset them Not particularly, no. It seems fairly unlikely, imo, that you'll switch from `absolute` to `fixed` or vice versa, which is the only case where the anchor positioning properties will continue to have an effect. If you do, I think there's a reasonable likelihood (like, roughly half the time, at least) that you do want to continue anchoring to the same element. Also if you do, there's a *very* high chance that you'll need to change your `inset` properties anyway (*those* seem highly unlikely to be useful with the same values in both modes), so changing more at the same time isn't unreasonable imo. (I said in the call that changing `inset` and `position-area` together is much more likely to be the thing that we need to do, honestly. Our own devrel people keep getting confused by this issue, because the scroll adjustment relies partially on `auto` insets.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10321#issuecomment-2330443972 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 September 2024 01:51:36 UTC