I really don’t agree with disabling GreaseMonkey, or Autolink. It’s up to the user how they wish to view the page.
You don’t see people moaning about those that decide to block adverts, do you?
I laughed a bit when -dean suggested it would be crazy (my words – not his) for users to view the web with JavaScript turned off, because all his web design relies so much on it! Some users do!! And Some users do it by accident (the stupid ones – and how many of those are there?)…the guy should at least have a non-javascript alert for his site visitors to be aware that they need to turn JavaScript on…and problem solved.
Also like the way he made that remark in comparison to someone visiting csszengarden with css-disabled…(but, isn’t this one of the accessibility perks of CSS – that it seperates style from content and allows non-css users the chance to still view the site clearly? So what’s the problem?!!)
*Laughs* Sorry, my comment ended-up having nothing to do with greasemonkeynuts at all! I’m aware of it though – and regard it as infernal pest that should be avoided at ALL costs! *Laughs* (Again)
Matt: I’m intrigued, why do you see Greasemonkey as an infernal pest? Personally, I think it’s the most interesting and exciting thing to happen to the web in a long time.
Dean Edwards’ way of disabling Greasemonkey will work exactly as long as Greasemonkey does not redefine createElement or anything else in the anonymous function context.
In the end, there is no evading Greasemonkey–and I don’t see why you would want that, anyway. Power to the people, and stuff.
On my computer (Firefox 1.0.3, Ubuntu), that page goes a step beyond disabling greasemonkey: it crashes Firefox a few seconds after I load the page!
It crashed Firefox for me as well (also 1.0.3, Ubuntu). Oh well.
Worked fine here…
Firefox 1.0.4
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050424 Firefox/1.0.4 (pigfoot)
It’s not built into the googlebar but you can disable the autolinks
http://www.searchguild.com/autoblink/
Which reminds me – I wanted to add this to my site.
I really don’t agree with disabling GreaseMonkey, or Autolink. It’s up to the user how they wish to view the page.
You don’t see people moaning about those that decide to block adverts, do you?
Yeah my site crashes Firefox on Linux:
https://bugzilla.mozilla.org/show_bug.cgi?id=288818
Oops!
I laughed a bit when -dean suggested it would be crazy (my words – not his) for users to view the web with JavaScript turned off, because all his web design relies so much on it! Some users do!! And Some users do it by accident (the stupid ones – and how many of those are there?)…the guy should at least have a non-javascript alert for his site visitors to be aware that they need to turn JavaScript on…and problem solved.
Also like the way he made that remark in comparison to someone visiting csszengarden with css-disabled…(but, isn’t this one of the accessibility perks of CSS – that it seperates style from content and allows non-css users the chance to still view the site clearly? So what’s the problem?!!)
*Laughs* Sorry, my comment ended-up having nothing to do with greasemonkeynuts at all! I’m aware of it though – and regard it as infernal pest that should be avoided at ALL costs! *Laughs* (Again)
Matt: I’m intrigued, why do you see Greasemonkey as an infernal pest? Personally, I think it’s the most interesting and exciting thing to happen to the web in a long time.
Dean Edwards’ way of disabling Greasemonkey will work exactly as long as Greasemonkey does not redefine createElement or anything else in the anonymous function context.
In the end, there is no evading Greasemonkey–and I don’t see why you would want that, anyway. Power to the people, and stuff.