[Webkit-unassigned] [Bug 150479] Expose public APIs for content filters

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=150479

Benjamin Poulain <benjamin at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #264149|review?                     |review-
              Flags|                            |

--- Comment #5 from Benjamin Poulain <benjamin at webkit.org> ---
Comment on attachment 264149
  --> https://bugs.webkit.org/attachment.cgi?id=264149
Patch

Hi Brian,

Public APIs need to be discussed internally and go through API review. The private API you are exposing was never designed to be public, we may not want to expose Content Blockers with that particular API.

Did you create radar for your feature request?
The first thing will be to discuss internally with the team at Apple to know if anyone objects a public API for Content Blockers. If there are not objection, we can start discussing an API.

The reason exposing API is a PITA is the long term cost of exposing something new. Once we expose an API, we restrict the freedom we have to change the implementation. Sometimes it has hurt us badly, which is why we try to avoid mistakes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151027/63d3b689/attachment.html>