- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 13:18:20 +0000
- To: public-css-archive@w3.org
The Houdini Task Force just discussed `[css-anchor-position] Invalidation of last successful position option in cases not in the spec`, and agreed to the following: * `RESOLVED: last successful position option is cleared if computed values changed in: 'position', 'position-try-*', any @position-try block referenced by 'position-try', or any property that is allowed in '@position-try', e.g. width` * `ACTION: TabAtkins: to ask anders` <details><summary>The full IRC log of that discussion</summary> <alisonmaher> fantasai: when we do fallbacks we try to make it sticky<br> <alisonmaher> ... until it is invalidated<br> <alisonmaher> ...when we need to we invalidate and maybe choose another fallback<br> <alisonmaher> ....three postions ??<br> <ChrisL> when the element is not absolutely positioned anymore<br> <ChrisL> when the computed value of position-try-fallbacks for the element changes<br> <ChrisL> when any @position-try rules referenced by the element's position-try-fallbacks changes<br> <alisonmaher> ...there are more cases that tigger invalidation<br> <alisonmaher> ...if position try order<br> <alisonmaher> ...or base style changes<br> <alisonmaher> ...when do we invalidate the fallback and can we spec it?<br> <fantasai> https://wpt.live/css/css-anchor-position/base-style-invalidation.html<br> <alisonmaher> TabAtkins: reacquainting myself<br> <fantasai> https://wpt.live/css/css-anchor-position/anchor-position-non-anchored-fallback.html<br> <alisonmaher> ...this is just about forgetting the last successful position<br> <alisonmaher> ...for position try order I have no problem adding to the the things that make us forget the last position<br> <alisonmaher> ...that makes sense<br> <alisonmaher> ...for altering the base styles that confuses me<br> <alisonmaher> ...the other changes that are possible are also part of the base style<br> <alisonmaher> ...I am confused why this test would check for other things changing<br> <alisonmaher> ...this comes from a Chromium issue<br> <alisonmaher> iank_: Rune has the context<br> <alisonmaher> fantasai: I don't know what's happening. Chrome has additional criteria we aren't aware of<br> <alisonmaher> fantasai: maybe it's reasonable but we should spec it<br> <alisonmaher> TabAtkins: if we spec tjhis any change to base styles should cause us to forget the last remebered position<br> <alisonmaher> fantasai: don't think you want that<br> <alisonmaher> ...maybe any styles in @position try or @position try values<br> <alisonmaher> TabAtkins: reasonable subset<br> <fantasai> s/@position try values/position-try properties/<br> <alisonmaher> ...I find it reasonable to amend to position try properties<br> <alisonmaher> fantasai: position try fallbacks or options<br> <fantasai> position-try-*<br> <TabAtkins> "allowed @position-try properties"<br> <fantasai> or @position-try rules that are used<br> <alisonmaher> fantasai: we should check for those<br> <alisonmaher> TabAtkins: ok with this<br> <fantasai> PROPOSED: last successful position option is cleared if computed values changed in: 'position', 'position-try-*', any @position-try block referenced by 'position-try', or any property that is allowed in '@position-try', e.g. width<br> <fantasai> RESOLVED: last successful position option is cleared if computed values changed in: 'position', 'position-try-*', any @position-try block referenced by 'position-try', or any property that is allowed in '@position-try', e.g. width<br> <fantasai> ACTION: TabAtkins: to ask anders<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12577#issuecomment-3210575175 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 13:18:20 UTC