InformAction Forums

I have, in my bookmarks toolbar, a little Javascript bookmarklet that should do a Google site search for whatever domain is serving the web page in the currently active tab. Instead, it doesn't work at all on real sites, even ones where I have enabled all the Javascript coming from the web page's domain, such as this one. Instead, the page just flickers, like it's trying to load the search page, but it stays right where it is. In fact, testing it now, the only pages I can confirm it to work on are about:blank and about:config.

As a further oddness, it does something to the little NoScript icon in the toolbar (yes, I have a toolbar while running Firefox 7.0.1, thank you very much): The script, in case you don't want to read the source, will first check to see if you have any selected text in the active tab; if you do not, it pops up a little window to ask you what terms to search for. While this window is up, the NoScript icon has a little red exclamation point (!) next to the blue-on-white S, as opposed to the usual 'just the blue-on-white S' or red slashed circle.

Here is the source code:
I have gone to about:config and enabled noscript.allowBookmarks, noscript.allowURLBarImports, and noscript.allowURLBarJS. I'm currently right now running Firefox 7.0.1 from the Ubuntu repos, but this also happens (essentially) the same way on the current Firefox from the Beta update channel.

WFM.
Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20100101 Firefox/8.0

Started off by doing a Reset (only cause I had no idea in what state my settings may have been in).

From here (not allowed): http://www.gena01.com/
HIghlighted: "Win32Pad"
Bookmarklet returned (as expected): http://www.google.com/search?num=100&q= ... in32Pad%22

While this window is up, the NoScript icon has a little red exclamation point (!) next to the blue-on-white S

I believe that expected behavior.
(As in like that is how NoScript is able to run bookmarklets, temporarily Allow Global, kind of thing. Believe I've read something to that effect here before.)

So, create a new test Profile, install NoScript & see if your bookmarklet works.

If it does, then perhaps some particular NoScript setting.
To try to find that, copy your original prefs.js into the test Profile, & test again.
If it then does not work, it would tend to point to a particular NoScript pref.

If it still works, then it may be some conflict with another extension?

Well, it works in a fresh profile with only NoScript installed. Does anyone have any ideas about what could be causing it?

Derleth wrote:Well, it works in a fresh profile with only NoScript installed. Does anyone have any ideas about what could be causing it?

If it works with only NoScript installed, then you have an "extension conflict" -- one or more of your other add-ons isn't playing nicely with NS.
Do the Standard Diagnostic, or just add back your add-ons one at a time, until you find the one that breaks it again. Discovering which one it is (one you can't live without, or one you don't mind uninstalling) will determine the next step.

Tom T.: I tried that for a while, but I'm lazy and changing the search URL to https://duckduckgo.com fixed the issue, so I'll have site search at my fingertips after all.

Which does suggest that it's related to whatever Google is doing that I'm blocking. Which also suggests it isn't something I'm going to fix at my end.

(In specific: Replace the google stuff with 'https://duckduckgo.com/?q=site:' and don't change anything else. Except maybe the bookmarklet name.)

Derleth wrote:Tom T.: I tried that for a while, but I'm lazy and changing the search URL to https://duckduckgo.com fixed the issue, so I'll have site search at my fingertips after all.

Which does suggest that it's related to whatever Google is doing that I'm blocking. Which also suggests it isn't something I'm going to fix at my end.

(In specific: Replace the google stuff with 'https://duckduckgo.com/?q=site:' and don't change anything else. Except maybe the bookmarklet name.)

I use https://ssl.scroogle.org myself. Hadn't heard of duckduckgo, but at a quick glance, it seems to offer the same advantages: No tracking, no profile-building, no cookies, logs shredded in two days instead of two years or never, etc.

Anyway, if you're happy, we're happy. Will mark this one as solved, and if anyone else has the same issue, here are two workarounds to consider.

Thanks for the report.