- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Feb 2023 17:26:14 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[scroll-animations-1] Phases for taller than scrollport subjects`, and agreed to the following: * ``RESOLVED: add `entry-crossing` and `exit-crossing` to handle things which could be taller than the scrollport`` * `RESOLVED: keep entry as entry` <details><summary>The full IRC log of that discussion</summary> <argyle> astearns: next issue, taller than scrollport stuff.<br> <argyle> bramus: essence of this issue boils down to the largest part of the issue, you cant do animations while they scroll into view or not when using the exisrting phases. this onlyu applies to taller than viewport subjects.<br> <bramus> https://github.com/w3c/csswg-drafts/issues/7973#issuecomment-1349970567<br> <argyle> bramus: fantasai suggests keep current phases but specify two extra phases, linked int his comment<br> <argyle> bramus: entry-crossing and exit-crossing, looks at subject itself while it's crossing that edge<br> <argyle> bramus: i dont have a visualization for it unfortunately. there's a spec adjustment that describes it<br> <astearns> https://github.com/bramus/csswg-drafts/commit/392a4deefdc546591ab48ed899aded52bd698467<br> <argyle> bramus: entry crossing would be subject taller than viewport, or any sized item, crosses the bottom<br> <argyle> bramus: until it's end edge coincides with the end edge of the scroller<br> <argyle> bramus: exit crossing is when the start edge of the subject coincides with the start edge of the scroller, until it moves entirely out of the scroller<br> <argyle> flackr: it's basically the other possible option when we decided the way we did to avoid the overlap of phases for trivial cases<br> <argyle> astearns: we expect people will still use entry and exit for most cases, but these new ones are for cases where it can be taller<br> <fantasai> illustration -> https://user-images.githubusercontent.com/213073/198659234-76702d8b-9770-43a0-9ee9-d81723e8c15b.png<br> <argyle> bramus: yes, this was a missing thing int he spec, and with this authors can do oanything they want<br> <ydaniv> SGTM<br> <argyle> astearns: any comments or concerns about adding more keywords?<br> <flackr> SGTM<br> <argyle> sgtm<br> <fantasai> +1<br> <argyle> RESOLVED: add `entry-crossing` and `exit-crossing` to handle things which could be taller than the scrollport<br> <astearns> ack fantasai<br> <Zakim> fantasai, you wanted to discuss follow-up question<br> <argyle> fantasai: we had discussed having the name of ranges be enter an exit or entry and exit. given we have entry-crossing, we should go with entry and exit.<br> <argyle> astearns: they should match<br> <argyle> fantasai: this new keyword tips things in the direction of entry being more appropriate<br> <argyle> flackr: i was going to say i dont love the names, but i dont have alternatives<br> <fantasai> note the current draft uses 'entry'<br> <fantasai> there's a issue asking if it should be 'enter'<br> <argyle> flackr: another way to think of this, is whether the element intersects the entry/exit edges of the scroller. but i dont think that helps us get a better name<br> <argyle> flackr: i'm fine to change to entry if that makes more sense<br> <argyle> fantasai: is it entry, i just want to close that issue<br> <bramus> q+<br> <argyle> astearns: resolve on keeping entry as entry<br> <astearns> ack bramus<br> <argyle> bramus: i found enter to match better, but english isnt my primary language. no scroll feelings<br> <bramus> q-<br> <argyle> astearns: enter is easier to spell to non english speakers<br> <argyle> fantasai: enter is a noun<br> <fantasai> s/enter/entry/<br> <argyle> astearns: my suggestion is we resolve now on keeping entry for consistency, but like everythihng, if peoeple come up with better ideas we can go ovoer this again in the future<br> <argyle> astearns: anyone have concerns with that direction? any objections to keep entry as entry?<br> <argyle> RESOLVED: keep entry as entry<br> <argyle> astearns: anything else?<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7973#issuecomment-1412441312 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 February 2023 17:26:15 UTC