On Wed, Dec 10, 2008 at 11:46 AM, Aaron Boodman <[EMAIL PROTECTED]> wrote:
> I've added a design doc for how the user scripts feature of extensions > will work: > > > http://sites.google.com/a/chromium.org/dev/developers/design-documents/extensions/userscripts Nitpick: Your grammar for host/path seems a little wrong. I think you need a mandatory "/" as the first character of the path. (Without this, I think "http://www.google.foo";, which you claim is invalid, is actually OK.) Dunno if you care that the current grammar allows illegal hosts/paths too. As to matching hosts without registry-controlled domains: You should make sure an author can code a script for an intranet site, e.g. "http://foo/";. Probably also numeric addresses ("http://192.168.0.1/";, I don't care so much about "http://123456789/";). For file:// support, why not allow "file" as a supported scheme, but not include it in the "*" list? Authors who wish to support it can explicitly add a match for it. I still think it would be nice to default to inject early, and inject at content loaded later (if we ever do some sort of "greasemonkey compat mode" we can flip the default for greasemonkey scripts). I say this because it presents the user a more seamless experience, but I'm clueless about actually writing these scripts, so perhaps this poses authors nasty challenges. PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
