- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 May 2019 15:25:15 +0000
- To: public-css-archive@w3.org
That looks good to me. Other key points from the discussion, as I understand it: - The property should have no side effects; it doesn't force a compositor layer on its own & doesn't change rendering for non-moving elements. - User agents would have some flexibility in deciding which types of movement _do_ trigger motion blur (for `auto` but also for `blur`). It could include scrolling motions as well as transforms and motion path. It wouldn't normally include changes that are implemented with repaints on each frame. - The exact blurring algorithms would be implementation dependent. When deciding which motions trigger blur, user agents should make reasonable trade-offs to create an overall smooth animation. - Adding this property doesn't prevent CSS adding directional blurring to `filter` (etc.) for more direct author control of smear/swipe effects, in the future. Next step would be to get feedback from implementers on how easy/hard this would be to implement & whether they're likely to do so if it gets spec'd. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3837#issuecomment-488314120 using your GitHub account
Received on Wednesday, 1 May 2019 15:25:17 UTC