Greasy Fork

Google hit hider does not block when searched from chrome address bar.

(Sorry for bad english) For example, i perma banned wikipedia and the script works fine when searched from "main google page",but does not when i type wikipedia in chrome address bar(google engine). Someone please help.

Hi fere, this is my script, so you can post on the script's page: https://greasyfork.org/scripts/1682-google-hit-hider-by-domain-search-filter-block-sites/feedback (Maybe Jason will move this post).

Could you copy the URL of your results page and paste it into a reply here?

For my test: https://www.google.com/search?q=wikipedia&rlz=1C1LENP_enUS496US496&oq=wikipedia&aqs=chrome.0.69i59j0l5.1155j0j9&sourceid=chrome&es_sm=93&ie=UTF-8

It takes a moment for that top result to be removed.

When typed from chrome address bar the script stops running,i have to refresh the page for it to properly work.And thanks for making this script.(Sorry for bad english)

Thank you for the screen shots. I've been trying to figure out how to get "Chrome Instant" to happen because that isn't how I've got Chrome set up. Hmm...

(Added) It seems to happen for some searches and not others, maybe 1 out of 5 times testing with a new user. When I reload, the page structure doesn't change, so it appears to be some kind of timing issue with how the content is injected into the page. I'll need to do a lot of testing.

I created a new user in Chrome and can reproduce this consistently. None of the Tampermonkey scripts which should run on a page actually run when "Chrome Instant" search is used. Here's a screencast of the problem: http://screencast.com/t/IJrZfKTq6j

The reason I didn't see it with my regular user account, is the advanced setting "Predict network actions to improve page load performance". I had turned that off because I didn't want Chrome retrieving pages in the background until I clicked the link to them. That little bit of speed improvement seemed to involve a significant sacrifice of privacy. You can read more about this setting here: Make webpages load faster (prerendering) - Chrome Help.

With this setting off in my new user, I get normal Google results pages where Tampermonkey is running. So my suggested workaround for now would be to turn off the preloading/prerendering feature.

I submitted a bug report to the author of Tampermonkey to see whether this can be fixed: http://forum.tampermonkey.net/viewtopic.php?f=17&t=1015

There is an updated beta version version of Tampermonkey available that should fix this issue. I won't be able to try it until "after hours" but there is a link in the first reply here: http://forum.tampermonkey.net/viewtopic.php?f=17&t=1015

Oh, it's in the Play/Chrome store here: https://chrome.google.com/webstore/detail/tampermonkey-beta/gcalenpjmijncebpfijmoaglllgpjagf