- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Sep 2023 12:46:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-anchor-position] Anchor positioning proposal comparison`. <details><summary>The full IRC log of that discussion</summary> <ntim> TabAtkins: Listed out all the use cases, and what proposals can do them well, not well, etc.<br> <astearns> updated list: https://github.com/w3c/csswg-drafts/issues/9117#issuecomment-1698431865<br> <flackr> q+<br> <astearns> ack flackr<br> <ntim> flackr: I don't see transitions between anchors, which none of the proposals cover, but is very common<br> <ntim> una: I see transitions between fallbacks<br> <ntim> dbaron: look at the second list that astearns linked to<br> <dbaron> Is there an item in that list for the sidenotes / doc comments use case?<br> <ntim> TabAtkins: you can animate between 2 distinct anchors, the problem is animating when what an anchor name refers to changes<br> <ntim> fantasai: transition between two anchor names is in the table<br> <nicole> https://docs.google.com/document/d/185yzaofuMP2p1KK00e2J0cmL8vAxOY3LF7NxhpjveRo/edit<br> <ntim> (what flackr was referring to)<br> <nicole> This is the document of examples<br> <ntim> TabAtkins: does anyone see something obviously missing in the table?<br> <dbaron> ntim: "anchor reference changes" is a confusing term because it can mean either "a change to which anchor is referenced" or "the anchor that is referenced changes (e.g., moves)"... and we care about both<br> <ntim> fantasai: the ability to style based on fallbacks<br> <emeyer> q+<br> <dbaron> s/ntim:/dbaron:/<br> <flackr> q+<br> <astearns> add https://github.com/w3c/csswg-drafts/issues/9332 to the list<br> <TabAtkins> https://github.com/w3c/csswg-drafts/issues/9332<br> <flackr> q-<br> <astearns> ack emeyer<br> <ntim> emeyer: multiple anchors is something I'm interested in, there is no issue<br> <ntim> fantasai: not in the issue, because Tab's proposal already covers it<br> <ntim> fantasai: Not sure if it's covered, but cascading behavior on the @try blocks is terrible<br> <TabAtkins> (it's on th elist of topics to discuss)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9117#issuecomment-1717561849 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 September 2023 12:46:08 UTC