Bug 153843
| Summary: | Inherited CSS property transitions happen in sequence instead of simultaneously | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brandon Smith <brandon.smith.945> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Minor | CC: | bfulgham, brandon.smith.945, dino, simon.fraser |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Mac | ||
| OS: | OS X 10.11 | ||
Brandon Smith
When both a parent and child element have the same transition configuration, and the property in question is changed on the parent (and inherited by the child), the child's transition will wait until the parent's has finished. If the child's property is changed directly - instead of being inherited - the transitions will happen at the same time. I've made a JSFiddle to illustrate (https://jsfiddle.net/brundon/32bLoLuw/2/). I've confirmed this happens in Chrome and Safari on OSX, and thought it might have been an obscure CSS spec quirk until testing it in Firefox and finding that it does not happen there.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brent Fulgham
Safari, Chrome, and Firefox all agree on rendering for this test case. I don't believe there is any remaining compatibility issue.