Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Simple javascript:alert() pasted into address input doesn't work.

Javascript is fully enabled in Noscript, "[ ] Disable bookmarklets" for untrusted sites is not selected.

It works if called from a bookmark, but it doesn't if I type bookmark's name in the address bar and select the address after it appears. This completely ruins the idea of bookmarklets / address bar js snipeets! This SUX!

share|improve this question
up vote 2 down vote accepted

There was a Firefox bug (656433) that removed the ability to run any JavaScript bookmarklet from the URL bar.

You now have to find a workaround, or run it from the Web Console (Web Developer -> Web Console). Make sure to remove the "javascript:" prefix if you run it from the Web Console.

You could also run it as a bookmark: create a new bookmark with the JavaScript statement as the URL. Then just "open" the bookmark on the page that you want to run it on.

share|improve this answer
It's actually not a bug but a feature request AFAIU. – Smit Johnth Mar 15 '13 at 0:54
There is no discrimination between "bugs" and "feature requests" within the Bugzilla software. They are all referred to as a separate bug, so for the sake of conformity.. – Wk_of_Angmar Mar 15 '13 at 18:40
Also, people don't typically like having "obtrusive" change logs popping up after every update, and with the number of changes between each release it's not really beneficial for Firefox when considering the average user. I'd also hazard a guess that a few number of users rely on using any bookmarklets. – Wk_of_Angmar Mar 15 '13 at 18:44
Even if, they should either make it work or not work, not it's working like retarded. <Also, people don't typically like having "obtrusive" change logs popping up after every update> - funny, that's exactly what 100% of plugins do, open their changelog window with ads unless you dig into settings and turn it off for every plugin. Thank god not in about:config. – Smit Johnth Mar 17 '13 at 3:14
Yeah, and in general people hate that. An appeal to popularity is a bad argument considering that the extension authors have a vested interest to include these change log popups to make more (advertisement) money. – Wk_of_Angmar Mar 17 '13 at 17:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .