W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

[csswg-drafts] [css-animation] Motion Blur (#3837)

From: Adam Argyle via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 Apr 2019 20:42:18 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-434476966-1555533737-sysbot+gh@w3.org>
argyleink has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-animation] Motion Blur ==
### Why
Professional polish of motion graphics often includes the application of motion blur. In most cases, it's a boolean toggled at the layer level, that then tells the engine to set a blur amount based on the speed of the pixels. This effect makes animations much closer to real life, among other nice benefits. CSS currently is incapable of such an effect. Instead, a strobing, ghosted type effect is often what we get instead.

Motion blur, as is found in motion graphic tooling like After Effects, is not possible with current filters because each pixel is evaluated, not the entire layer. Each pixel is evaluated for velocity and blurred contextually. CSS blur() can only apply to the entire layer.

### Example
**No** motion blur (pardon 15fps gif quality..)

**With** motion blur

### Proposal
**I'd like to propose a way for developers to opt into motion blur on the web**. I think it should be handled by the GPU, and require little effort from the implementor. 

.animated-layer {
  animation: rotate-forever 1s linear infinite;
  motion-blur: blur; /* inherit | initial | none | blur */

@keyframes rotate-forever {
  to {
    transform: rotate(1turn);

### Implementation Details

- default value is none
- in some cases it will create no effect (not enough speed, etc)

### Assertions
- effect is limited to GPU accelerated animations/transitions

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3837 using your GitHub account
Received on Wednesday, 17 April 2019 20:42:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:46 UTC