[Webkit-unassigned] [Bug 117823] [Qt] Add interface API for origin whitelisting

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 30 03:27:24 PDT 2013


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





--- Comment #20 from Jocelyn Turcotte <jocelyn.turcotte at digia.com>  2013-07-30 03:27:10 PST ---
(In reply to comment #18)
> Yes, this API should not be attached with a particular origin considering the current implementation in SecurityPolicy. But I would suggest to retain this and be implemented as a static API. It will come handy in a case where application wants to flush an entire set in one go instead of iterating though a list of origins. Please let me know your opinion.

I would prefer that we do it either the ideal way (fix SecurityPolicy to support clearing for a specific security origin) or avoid it (not add the API).

If you need the functionality in your application now we can do a compromise and add the static API, but otherwise I think that the risk isn't worth it. If we add the static API and that the code changes underneat later (because it's not ideal), we'll have to suffer consequences that might not be worth the candle.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list