- From: Aleksandar Totic via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Jan 2019 18:26:11 +0000
- To: public-css-archive@w3.org
Verbal comment by @bfgeek about observing 'scroll-box': Ian mentioned that there is an interesting implementation difference between `scroll-box` and `content-box`/`border-box`. This might be an argument against adding `scroll-box`. `scroll-box` can be affected by compositor animations, and in the future, Chrome might want to modify scroll-box without performing style/layout. For example, if there is a css animation that affects scrollbar, animation and scrollbars can be repainted in the compositor thread without performing style/layout on the main thread. Edge already does this. If we were to add ability to watch scroll-box, then scrollbox animations would have to be performed back on the main thread, so that RO callbacks can be called. Or we could say that RO callback will not get called if scroll-box changes on the compositor thread... -- GitHub Notification of comment by atotic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3326#issuecomment-452803023 using your GitHub account
Received on Wednesday, 9 January 2019 18:26:12 UTC