On Thu, Apr 23, 2009 at 4:48 AM, Lex1 <[email protected]> wrote:
>
> Following the «run-at document-start» it was possible and I have made
> some extensions (http://userscripts.org/scripts/show/46974).  But now
> there are some problems:

Thanks for giving it a try.  As you likely know, the extensions API is
quite early.  Much of what you mention is already in development or
planned.


> 1) Need gui. At least item menu. User must have a convenient way to
> run adblock to blocking ads on the site, or disable flashblock on
> youtube. And yet there is only one (?) way to do this - to use
> hotkeys.

Of course.  The first bit of UI you'll likely see some support for is
simple toolstrips.


> 2) Need localStorage. Without localStorage, I was forced to use
> cookies, because «Gears» looks slow.

Gears isn't any slower than local storage will be, but it has some
issues in that it requires UI to enable it, so it's not practical for
content scripts.

Local storage and HTML5 databases are in progress.  When they land in
Chrome, they'll be immediately usable by extensions.  Lack of storage
is definitely one of the big limiting factors for extensions today.


> 3) Need method for blocking scripts. Maybe similar to Opera's
> «BeforeExternalScript».

This is on our radar.


> 4) Maybe «run-at document.head-start» and «run-at document.body-start»
> will be useful. Of course we can use the «run-at document-start +
> setTimeout», but it would be convenient and reliable.

>From document-start, you can add event handlers that can accomplish
what you're looking for.  You don't need setTimeout.


> P.S. I know that «This extension system is not ready yet», but «API
> Wish List» does not contain all of these wishes and they can be
> useful.

Our list doesn't contain things that are covered by existing HTML
standards work like local storage and databases.


Erik

--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---

Reply via email to