| Summary: | USE(CONTENT_FILTERING) should be ENABLE(CONTENT_FILTERING) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Andy Estes <aestes> | ||||
| Component: | New Bugs | Assignee: | Andy Estes <aestes> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | benjamin, cmarcelo, commit-queue, japhet | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 128858 | ||||||
| Attachments: |
|
||||||
|
Description
Andy Estes
2014-07-30 16:15:19 PDT
We now support two different platform content filters, and will soon support a mock content filter (as part of webkit.org/b/128858). This makes content filtering a feature of WebKit, not just an adoption of a third-party library. ENABLE() is the correct macro to use for such a feature. Created attachment 235779 [details]
Patch
Committed r171826: <http://trac.webkit.org/changeset/171826> |