Bug 118539
| Summary: | [CSS Filters] Filter function should not be accepted without arguments | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dirk Schulze <krit> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | achicu, dino, mvujovic, simon.fraser |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Dirk Schulze
At the moment most filter functions don't need to have values like blur(). This is not appropriate CSS style. The filter function should not be accepted.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Dirk Schulze
Is that something that we can fix for the prefixed versions of -webkit-filter? I really hope so, because the code can not be isolated very well later and would require a lot of property name checks.
Simon Fraser (smfr)
Can you be more specific about the issue here?
Dirk Schulze
(In reply to comment #2)
> Can you be more specific about the issue here?
currently we accept:
-webkit-filter: blur() contrast() brightness();
The functions don't have any meaning without arguments and this is usually not allowed for CSS functions at all. The Filter Effects spec doesn't allow functions without arguments either.