Apologies is this shows up a 2nd time, it seems like my first reply
didn't make it (but it could be that I accidentally closed the window
before hitting Send).

It seems that the 2.0.159 release (and the trunk builds that make it
up) changed User Script behavior significantly.

It used to be that I could have a common.user.js and then call
functions that were defined within "common" from other scripts (or
from the JS console). Now, it seems like Chrome/Chromium reads the
script, executes it, and flushes it.

Bluntly, that sucks. Hopefully that's a bug and will be fixed,
otherwise I'll just stick with the build before that changed :) When
I'm not at work I plan to file a bug report on that, because I think
it's broken behavior.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to