[webkit-dev] browser extensions

[Patrick Mueller]

Yup, it's easy to draw the line of "what goes into WebKit" for things 
like browser extensions.  It does kind of raise the question whether 
there should be some other "layer" between (alongside?) WebKit and user 
agents, where things like extensions, debuggers, etc, might live.

Aaron Boodman wrote:
> Extensions logically fall outside the boundary of the rendering
> engine, and that is the way we've approached in Chromium, too. But
> since Chromium extensions are basically just web pages with a few
> extra APIs added, there is a relatively obvious path to compatibility
> and even sharing code if other browsers ever wanted to adopt them.
> 
> - a
> 
> On Wed, Apr 15, 2009 at 9:06 AM, Patrick Mueller
> <pmuellr at muellerware.org> wrote:
>> Now that the Chrome folks have talked about extensions, I thought I'd ask
>> what the story/plan is for WebKit.
>>
>>  http://www.aaronboodman.com/2009/04/content-scripts-in-chromium.html
>>
>> So ... I guess the first question is, are extensions considered out-of-scope
>> for WebKit?  As in, more of a browser thing than a toolkit thing?  It's easy
>> to see this going either way; 'portable' extensions will be hard, especially
>> given any browser specific things you might want extensions to do; on the
>> other hand, having all the WebKit consumers out there having a common
>> extension story would obviously be very useful.
>>  ...

-- 
Patrick Mueller