Home/ Questions/Q 6468873
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T05:55:50+00:00

I’ve attempted to make some modifications to a userscript to enable it to work

  • 0

I’ve attempted to make some modifications to a userscript to enable it to work under Chrome, but when I drag it into Chrome’s window in order to install it, a dialog pops up and says ‘Invalid Script Header’.

I’ve tried to use the Developer Tools, and built-in Javascript Console, to debug any errors occurring, but nothing appears to list any information.

Console.app does not list anything meaningful, except for the same error message I already know.

[0x0-0x2d02d].com.google.Chrome: [346:1547:16686819618022:ERROR:extension_error_reporter.cc(55)] Extension error: Invalid script header.

How can I reasonably debug this error message and figure out what about the header is incorrect?

I’m using Chrome 15.0.861.0 on the dev channel, under OS 10.7 Lion.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I finally stumbled across the answer to this question, amusingly via a Chromium Bug Report.

    As it turns out, the answer to my question was in the (significantly brief) Userscript Documentation for Chrome page.

    With Greasemonkey-style @include rules, it is not possible for Chrome to know for certain the domains a script will run on (because google.* can also run on google.evil.com). Because of this, Chrome just tells users that these scripts will run on all domains, which is sometimes scarier than necessary. With @match, Chrome will tell users the correct set of domains a user script will run on.

    As it turns out, I had been using @match http://*musicbrainz.org in an attempt to match www.musicbrainz.org as well as musicbrainz.org, but per the quoted text, that doesn’t save you from accidentally matching evilmusicbrainz.org. So, my solution was to use two lines:

    @match http://*.musicbrainz.org
@match http://musicbrainz.org
    • 0