Comment #10 on issue 24601 by bugdro...@chromium.org: Move security related
methods out of WebKit.h
http://code.google.com/p/chromium/issues/detail?id=24601
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=29639
--
Updates:
Status: Started
Comment #9 on issue 24601 by m...@chromium.org: Move security related
methods out of WebKit.h
http://code.google.com/p/chromium/issues/detail?id=24601
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or
Comment #8 on issue 24601 by aba...@chromium.org: Move security related
methods out of WebKit.h
http://code.google.com/p/chromium/issues/detail?id=24601
Out of curiosity, why make the API static methods? It seems like we might
as well make them instance methods.
They can always call static
Updates:
Status: Assigned
Owner: m...@chromium.org
Comment #7 on issue 24601 by da...@chromium.org: Move security related
methods out of WebKit.h
http://code.google.com/p/chromium/issues/detail?id=24601
(No comment was entered for this change.)
--
You received this message bec
Comment #6 on issue 24601 by da...@chromium.org: Move security related
methods out of WebKit.h
http://code.google.com/p/chromium/issues/detail?id=24601
static methods on a class named WebSecurityPolicy it is!
--
You received this message because you are listed in the owner
or CC fields of thi
