- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 May 2023 23:18:03 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `https://github.com/w3c/csswg-drafts/issues/8694`, and agreed to the following: * `RESOLVED: We will accept this PR and close the issue` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: https://github.com/w3c/csswg-drafts/issues/8694<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/8694<br> <dael> flackr: With view timelines we have named ranges that are related to the position and size of their subject within their scroller<br> <dael> flackr: This means that if the position or size changes the named range can change which changes animation progress and visual output<br> <dael> flackr: Per spec no update if the size or postion changes. Proposing we detect when this happens. It's similar to when we detect new timelines. It would be if it moves or changes size and we trigger a new layout cycle<br> <dael> flackr: I have a spec PR to make the change. main point is condition I noted and that it does it after resize observer and resize observer might change which we would want to respond to<br> <dael> flackr: Prop is Accept the PR that adds a change in position or size of subject as a condition to do a layout cycle<br> <dael> astearns: you have people commenting on issue and PR but not calling out changes<br> <dael> flackr: Discussed with iank_ who I think is on call<br> <dael> astearns: Any concerns or questions?<br> <dael> astearns: Obj to accept the PR?<br> <dael> vmpstr: What are implications to updating timeline. Can sizes change? Asking because doing this after resize observer means if updating can change size the size observation has to be on next frame<br> <dael> flackr: Size can change<br> <dael> flackr: It's generally frowned upon to animate size or layout and expect frame perfect<br> <dael> flackr: Trade off if we run before resize observer where we wouldn't guar. the timeline is correct or after<br> <dael> astearns: Is that enough of an answer?<br> <dael> vmpstr: I think that's fine. Just have an issue later on the agenda that's similar for non-timelines<br> <dael> astearns: Anything else on this issue?<br> <dael> astearns: Prop: We will accept this PR and close the issue<br> <dael> astearns: Obj?<br> <dael> RESOLVED: We will accept this PR and close the issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8694#issuecomment-1533872034 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 May 2023 23:18:05 UTC