On Fri, Dec 12, 2008 at 5:06 PM, Aaron Boodman <[email protected]> wrote:
> > I still think it would be nice to default to inject early, and inject at > > content loaded later. > > I want it to be easy to "upgrade" Greasemonkey scripts to extensions. > Changing the injection point would work against this. I don't think > the default injection point will prevent too many people from > realizing they can inject earlier if they want to. I guess it depends on whether you feel early injection, in the abstract, is significantly better than later injection. I do, and I figure that the number of total future user scripts is large compared to the number of existing GM scripts, so we should make life better for those future scripts at the expense of the current ones. If you think the two are not much different at all, defaulting to late injection seems fine. In general, I would like to make life easy on "upgraders", but I think there's some advantage to having one or both of two options: * Something that automatically runs existing GM scripts exactly as they intended to be run, regardless of default settings for user scripts * Something that rejects existing GM scripts but helps walk users through how they can change their script to make it compatible The option I'm explicitly leaving out is "make user scripts close to GM scripts, but not quite the same, so some things work and some don't". It seems like all-or-nothing (or best of all, both of those modes) is a better model for backwards compat. 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 -~----------~----~----~----~------~----~------~--~---
