[Webkit-unassigned] [Bug 37578] [Chromium] Consider implementing addOriginAccessWhitelistEntry method

[bugzilla-daemon at webkit.org]

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





--- Comment #9 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2010-04-28 13:31:11 PST ---
(From update of attachment 54566)
WebKit/chromium/src/WebSecurityPolicy.cpp:69
 +  void WebSecurityPolicy::unwhiteListAccessFromOrigin(const WebURL&
sourceOrigin,
Why not use the same name as the method on SecurityOrigin?  I have the same
question about whiteListAccessFromOrigin.

Oh, I see... in r57535, SecurityOrigin::whiteListAccessFromOrigin was renamed
addOriginAccessWhitelistEntry :-(

How about writing a patch that switches us over to the same method names as
SecurityOrigin so that we can avoid the awkward sounding "unwhiteListFoo"
method name?

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