Yes, making changes as discussed in bugzilla, plus removing
registerURLSchemeAsLocal would be a fine direction.
- WBR, Alexey Proskuryakov
On 12.04.2009, at 22:58, Aaron Boodman wrote:
It sounds to me like our current patch is the best fit because it fits
our needs, will work with
Ok, just to close the loop here, it looks like the preference is to do
the refactor of permission checking from XHR to
DocumentThreadableLoader, and then put the methods I proposed for
SecurityOriginClient on FrameLoaderClient instead.
I'm not sure who will get to the refactor first -- David,
It sounds to me like our current patch is the best fit because it fits
our needs, will work with Chromium's out-of-process workers, plus it
allows us to remove FrameLoader::registerURLSchemeAsLocal() as Alexey
requested. It has the downside that the client will get called on
multiple threads, but
On Thu, Apr 9, 2009 at 9:50 PM, David Levin le...@google.com wrote:
On Thu, Apr 9, 2009 at 9:03 PM, Alexey Proskuryakov a...@webkit.org wrote:
On 09.04.2009, at 22:38, Aaron Boodman wrote:
The local scheme feature is actually more powerful than just XHR
If you only need extensions to do
On Wed, Apr 8, 2009 at 11:53 PM, Alexey Proskuryakov a...@webkit.org wrote:
On 09.04.2009, at 1:23, Aaron Boodman wrote:
Rafael Weinstein, who is working with me, consulted with Adam Barth
and submitted a patch based on his ideas
https://bugs.webkit.org/show_bug.cgi?id=24853 for this a few
I have some relevant context that I'll add.
On Thu, Apr 9, 2009 at 12:38 AM, Aaron Boodman a...@chromium.org wrote:
On Wed, Apr 8, 2009 at 11:53 PM, Alexey Proskuryakov a...@webkit.org
wrote:
On 09.04.2009, at 1:23, Aaron Boodman wrote:
Rafael Weinstein, who is working with me,
On 09.04.2009, at 11:38, Aaron Boodman wrote:
Chromium extensions run in the same scheme (chrome-extension://), but
they do not run in the same origin. They all have unique origins of
the form chrome-extension://extension-id/. Security origin is scheme
+ host + port.
OK, I didn't know that
Adding back webkit-dev...
On Thu, Apr 9, 2009 at 11:36 AM, Aaron Boodman a...@chromium.org wrote:
Ok, so if I may sum up the conversation so far:
* A static call out to a client is ugly, but OK as a temporary measure
* You would like to see this mechanism replace the local scheme
thing that
On Thu, Apr 9, 2009 at 9:03 PM, Alexey Proskuryakov a...@webkit.org wrote:
On 09.04.2009, at 22:38, Aaron Boodman wrote:
The local scheme feature is actually more powerful than just XHR
If you only need extensions to do XHR, why not just make them use
cross-origin XHR? That way, the
Hello all,
I'm working on adding extensions (aka Add-Ons) to Chromium. One
thing we want to enable these extensions to do is to make limited
cross-origin XMLHttpRequests.
Rafael Weinstein, who is working with me, consulted with Adam Barth
and submitted a patch based on his ideas
10 matches
Mail list logo
