- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Sat, 17 Sep 2022 00:17:03 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `scope of named timelines`. <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: scope of named timelines<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/7047<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/7047#issuecomment-1239820755<br> <TabAtkins> fantasai: we talked about the scop eand came up with a default answer<br> <TabAtkins> fantasai: also what we might do to give power to people who want to do something more far-ranging than just "prev sibling" or "ancestor"<br> <TabAtkins> fantasai: so i came up with a suggestion to declare a timeline name but not attach it to a scroll container, and then attach it to one in the sibling/descendants<br> <TabAtkins> fantasai: suggestion is a property called scroll-timeline-attachment<br> <TabAtkins> 'local' is the default, binds to the element you're on<br> <TabAtkins> 'defer' will declare the name, but attach it to somethign else<br> <TabAtkins> fantasai: And another element can say "attach me to the timeline" of a given name<br> <TabAtkins> fantasai: so if i want a global scope<br> <TabAtkins> fantasai: can se the scroll-timeline-name:foo on the root , and scroll-timeline-attachment:defer<br> <TabAtkins> then on something else in the tree set scroll-timeline-name:foo and scroll-timeline-attachment: ancestor<br> <TabAtkins> fantasai: and it'll attach to that timeline scoped to the root<br> <TabAtkins> fantasai: i'm ambivalent about putting this in current spec, but wanted opinions on idea<br> <flackr> q+<br> <TabAtkins> zakim, open queue<br> <Zakim> ok, TabAtkins, the speaker queue is open<br> <TabAtkins> flackr: two thoughts<br> <TabAtkins> flackr: if you can name a timeline that's deferred, i don't think there's any need for the ancestor selection anymore, bc you could just name that timeline?<br> <TabAtkins> fantasai: defer says you're planning to attach the name to something else<br> <TabAtkins> fantasai: but if the element is also a scroll container<br> <TabAtkins> fantasai: it doesn't actually bind the timeline to its own scroller<br> <TabAtkins> flackr: okay so i misunderstood, 'ancestor' is the name lookup<br> <TabAtkins> flackr: yeah i proposed something similar earlier<br> <TabAtkins> flackr: so two, we havne't explored this idea too far yet, t5o see if there's a need for it<br> <TabAtkins> flackr: i guess it sovles every use-case since you can do global timelines<br> <TabAtkins> flackr: but i'm interested to see in practice how often people need these other scopes<br> <TabAtkins> flackr: anyway if we do need this power, i think this is a reasonable approach<br> <TabAtkins> astearns: maybe this could be an open issue to put in the next level if needed?<br> <TabAtkins> fantasai: yup<br> <TabAtkins> astearns: unless it would be good to put in the current draft to get more eyes on it, and punt if needed later<br> <TabAtkins> fantasai: i defer that judgement to flackr<br> <TabAtkins> flackr: I think we can add this later<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/7759<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7759#issuecomment-1249954588 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 17 September 2022 00:17:05 UTC