Bug 113140
| Summary: | [CSS Filters] There are two "filter" properties in WebKit | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexandru Chiculita <achicu> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | dino, krit, simon.fraser, syoichi |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 68469 | ||
Alexandru Chiculita
There are two "filter" CSS properties in WebKit:
1. "filter" - parsed for SVG filter
2. "-webkit-filter" - parsed for the CSS filter used in HTML content
The problem is that the value of one is not going to affect the other. From WebKit's point of view they are completely different CSS properties.
Some frameworks like prefixfree are detecting that "-webkit-filter" can be unprefixed just becaue there is a "filter" property available. However, that will fail because the SVG filter is not used in HTML and also has just a subset of the CSS Syntax.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexandru Chiculita
Link to the original bug in prefixfree: https://github.com/LeaVerou/prefixfree/issues/76
Dirk Schulze
Eventually -webkit-filter will get a subset of filter and vice versa.
Simon Fraser (smfr)
This was resolved a long time ago.