Bug 143601 - Unprefixed transition: filter is accepted by Safari but does not work
Summary: Unprefixed transition: filter is accepted by Safari but does not work
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-10 04:27 PDT by Tom
Modified: 2022-07-14 13:56 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom 2015-04-10 04:27:34 PDT 
Example URL:
http://jsbin.com/zabusuhese/1/edit?html,css,output

Steps to reproduce the problem:
1. create a div, apply the CSS: filter: brightness(100%); transition:filter;
2. set the hover state to filter:brightness(120%);
3. follow the above steps, replacing filter with -webkit-filter

What is the expected behavior?
both divs behave the same

What went wrong?
the unprefixed transition: filter did not work

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? works in Firefox
Comment 1 Simon Fraser (smfr) 2015-04-11 09:11:21 PDT 
Dean, with this:

transition: -webkit-filter 0.3s;
transition: filter 0.3s;

should we be smart enough to ignore the second rule with the invalid transitioned property name?
Comment 2 Tom 2015-04-14 06:17:44 PDT 
It seems the solution is to use a comma separated list of transitions, instead of expecting the supported transition property to overwrite successfully:

https://code.google.com/p/chromium/issues/detail?id=475865
Comment 3 Brent Fulgham 2022-07-14 13:56:39 PDT 
Safari and Chrome agree on rendering for this test case. I don't believe there is any remaining compatibility issue.