It seems that after updating to 8614 today (2.0.159), the behavior of User Scripts has changed significantly.
It used to be that I could define a function in, say, common.user.js and then use those functions in the Javascript console and in other user scripts. After updating, that doesn't work any more. Instead, it now seems that the user script engine reads the script, runs whatever is there and then flushes it. Maybe that was done to keep scripts from stepping on each other, but it means I can't have a common library and it means I can't write utility functions to run from the JS console. I'm going back to the version beforehand until hopefully it is reverted or fixed, and if it isn't fixed then I'll just stick with that version forever (even if it does have the annoying shrinking tabs). On Jan 26, 12:47 pm, Aaron Boodman <[email protected]> wrote: > On Mon, Jan 26, 2009 at 9:16 AM, jadavis01 <[email protected]> wrote: > > I am having trouble getting javascripts to initiate in Chrome/ > > Chromium. I'm not getting any errors, I just am not seeing any .js > > files being read/implemented in Chrome or Chromium. > > I have tried using --enable-greasemonkey or --enable-user-scripts in > > the target area of the shortcut. I have also tried running directly > > from the start menu "run" box using either of those two switches. > > I have tried loading the .js files into C:\scripts and also into C:\... > > \chrome\defaults or C:\...Chromium\defaults folders. > > Please double-check that you have followed these instructions, > exactly:http://dev.chromium.org/developers/design-documents/user-scripts. > Double-check the directory that you are using. It is easy to forget a > component of the path. > > > I have also tried using Greasemetal with no results happening. > > The javascript is all "canned" .js from userscripts.org. Most I have > > tried are applied to Gmail, like changing the delete button to red > > color or merging Greader in Gmail screen. Some are more Chrome > > oriented. > > I have read that many of the scripts are written for Firefox, Opera or > > Safari and don't work in Chrome/Chromiuim. I have tried some that are > > working for other people in Chrome. > > It's true that some scripts that are written for Firefox won't work > with Chrome, but it sounds like that isn't the problem you're seeing. > > - a --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
