Bug 50279
| Summary: | Allow transition-delay to affect non-animatable properties | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | cmarrin, dino, simon.fraser |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Simon Fraser (smfr)
It has been suggested that non-animatable properties should respect transition-delay, to allow the author to control when they change.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Chris Marrin
So, if you want an image to change after a period of time the logical thing to do would be to go:
transition-property: background-image;
transition-delay: 2s
But this won't work since you need a transition-duration. Seems like the better model would be to use a step function and set the transition up like any other property. Then all non-animatable properties would always use a step timing-function, either implicit or explicit. Then you'd set it up like this:
transition-property: background-image;
transition-duration: 2s;
transition-timing-function: step-end;
(I don't remember the step function syntax, but you get the idea).
I think this makes more sense and I think it would be easier to integrate this with other transitions.
Chris Marrin
So maybe a better title for this bug is "Allow non-animatable properties to animate with step timing-function"?
Simon Fraser (smfr)
Or we still respect the delay even if the duration is zero?
Dean Jackson
*** Bug 65488 has been marked as a duplicate of this bug. ***