- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2023 15:43:07 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[scroll-animations-1] ViewTimeline values of startOffset/endOffset in RTL writing mode`, and agreed to the following: * `RESOLVED: SLA uses logical interpretations of scrolling (rather than scrollLeft/Top always)` <details><summary>The full IRC log of that discussion</summary> <fantasai> s/Topic/Subtopic/<br> <TabAtkins> flackr: on SL timelines we have start-offset and end-offset giving resolved scroll position<br> <TabAtkins> flackr: right now i think they're aligned with scrollTop and scrollLeft, so they're not WM-aware<br> <TabAtkins> flackr: The math works out fine with potentially negative ranges<br> <TabAtkins> flackr: But question is if they should be logical, or stay aligned?<br> <TabAtkins> fantasai: and you brought up suggestion that maybe we need logical scroll offset accessors<br> <TabAtkins> ydaniv: We have some logical options for the visual viewport<br> <TabAtkins> fantasai: I feel like it would be nice ot have logical accessors on the element, and also made this logical as a result.<br> <fantasai> TabAtkins: If you're RTL< it defaults to being scrolled all the way to the right<br> <fantasai> TabAtkins: So my opinion is that the default behavior should match the experience of the person working with it<br> <fantasai> TabAtkins: even if the accessors don't yet exist<br> <TabAtkins> flackr: sure, we can go with logical, and have a followup to do logical accessors on scrollports<br> <TabAtkins> astearns: so proposed resolution is that for SLA we use the logical interpretations of scrolling?<br> <TabAtkins> flackr: yep<br> <fantasai> wfm<br> <TabAtkins> ydaniv: yeah sounds good<br> <TabAtkins> RESOLVED: SLA uses logical interpretations of scrolling (rather than scrollLeft/Top always)<br> <TabAtkins> astearns: And flackr will raise a separate issue for logical scroll-position accessors<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7752#issuecomment-1476475422 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 March 2023 15:43:09 UTC