thx KosciaK - bug fixed

the Google evolves permanently - they have changed a little bit theirs page that's why script stopped working - now it's fixed

Poland has different date pattern: dd-mm-yyyy hh:mm:ss CEST

this proper "re" for Poland is:

{ re: /(^(cgi\d*|www)\.ebay\.pl)$/i,
// Poland: dd-mm-yyyy hh:mm:ss CEST
date: function (strDate) {
var match = /^\D*(\d?\d)\W+(\d?\d)\W+(\d{2,})/i.exec(strDate);
return (match ? (new Date(getFullYear(match[3]), match[2] - 1, match[1])).toDateString()
: strDate);
},
time: function (strTimeWithZone) { return strTimeWithZone.replace(/CEST.*/, "GMT+2"); },
days: "d",
local: "local"
},


nice script - thanks for your work!

hi CustomizeGoogle! - check your mailbox

@Per Eriksson

if course it is - dive into code and find the line

document.body.addEventListener('dblclick', dblClickEvents, false);

at the end of the script an change this line to this:

dblClickEvents();

thats all

@Dawudd
imho efficiency of these two script is comparable - I've made rewriting in this way due to consistancy with CustomizeGoogle

nice piece of code, but due to some bug on Google Images site - using this script you miss some of the search results: automatic retrieving "next" link from the site source will cause miss of a few images - try to change the size of the browser window then you see different results for the same query - this is because page displays different number of images on one page (depending on window size) but doesn't change "next" link href - I discovered this strange behaviour when writing my own autopager only for Google Images - you can avoid this failure by counting number of displayed images and then calculating "next" link href by userscript not by page - like my script http://userscripts.org/scripts/show/8433 does

i almost do not use keyboard during researching - most of the search keys come from clipboard so lack of the search button is something really awkward for me

sorry, but this is crap - this loop:
for (var i = 0; i < results.length; i++) {
scripts = results[i].getElementsByTagName('script');
if(scripts.length > 0){
for(var i=0; i<scripts>
scripts[i].parentNode.removeChild(scripts[i]);
}
}
is absolutely useless!
I've updated this script: simplified and accelerated - http://userscripts.org/scripts/show/8430