I can't think of any time when chrome URLs were (intentionally?) scriptable, and I can't ever see them becoming so. It's a gaping security hole.
On Thu, Jan 2, 2014 at 10:47 PM, Scott Doherty <[email protected]> wrote: > Greasemonkey scripts used to have scope inside the Update > Scanner<https://addons.mozilla.org/en-US/firefox/addon/update-scanner/?src=userprofile>addon's > results. The U.S. addon produces a chrome://updatescan/content/... > kind of URL and now Greasemonkey will not apply scripts within the scanned > pages. Does anyone have any insight as to how I might script into that > scope or override something that might have changed? Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "greasemonkey-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/greasemonkey-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/groups/opt_out.
