thanks for the quick fix scott

Thanks Pete0r

Thanks for the fast response.. this is one of my favorite scripts!

I removed that line and added support for google.co.uk/reader

it seems reason is in "unsafeWindow.AK();" line

maybe it throws an exception

I'm getting the same error. I have other scripts, but if I turn them all off and just have GRM up, it still produces this behavior. Page is completely blank. I can hit W to see the menu at the top, but that is it. U has no effect.

hmm its still working for me, anyone else having a problem?

do you have any other scripts installed?

The skin seems to be broken as of today. When Reader loads, it just displays a blank page. If you press 'w', some of Google's inter-site navigational elements appear at the top of the page, but none of Reader's UI.

has anyone had any layout issues, I could see a bit of the google logo in the top left today but after refreshing the I couldn't replicate it.

Just thought I'd let you know unsafeWindow.AK() changed to BK().. currently my solution though is to trigger the "u" keyboard event two times, hides/shows the nav-bar, this way googles own JS tells it to refresh the view.

Another solution would be to use regexp to search for the function and trigger it.

Thanks Danny, I'm glad I could help

Awesome! Kudos for the speedy fix. This is my favourite script by far.

Hi Danny, I've just updated with a fix to ignore Cmd+W and Alt+W in addition to Ctlr-W let me know if you have a problem

One thing I find REALLY ANNOYING which didnt happen before - Command + W on the mac (Same as Control + w) does not close tab anymore, but instead hides/shows the header. I'm using Firefox 3.0

Just updated to remove the blue border around news items

Thanks merttt, it's really cool to hear, sadly there's no greasemonkey on my windows mobile.

I'm not sure what to do with those boxes, I just leave the subscriptions collapsed all the time but I could see how its a problem since it doesn't scroll

Thanks anemos, I've added that in there and your right this is the only place its documented

Hei, great script. I've got an idea for improvement though!

As i noticed it doesn't recalculate windows size whenever you hit "w" so some elements are hidden in "full screen". I'm quite sure this ISN'T a feature, but a bug. A solution is to add this at the end of function toggle_gr():

unsafeWindow.AK();

unsafeWindow basically says to use the pages own javascripts, not limited to the functions within greasemonkey. Now don't ask me how i found out that this function recalculates the size of the window, it was like finding a needle in a haystack, i guarantee! (doubt it is documented anywhere, and GReaders .js file is hellish..)

Hei Scott and thanks. It was good mental exercise to work out what worked :)

Hi cintra, just got off a 14h flight or I would've been able to help earlier. As far as I know lifehacker haven't updated with the 2.0.0.12 fix yet but Gina knows about it so you might want to use this one til you see and update available

OK, now I have it. When using Better Greader's (0.2.1) Minimalistic skin w doesn't work.

However if I choose no skin, and use the Minimalstic script instead w works well.

Could be that Better Greader needs to update their skins..

Thanks anyway. Your skin helps make Google Reader a lot better!

Back again.. have just come back to the iMac during which time it was Sleeping, and blow me but w is working solidly now..

I'm afraid the w problem still exists here on 2.0.0.12 Leopard 10.5.2 - u works ok all the time. w has done on this version IIRC, but right now it simply blanks the mouse cursor and thats all :)

Any chance to allow choice of own letter?

the w key is fixed, the problem with firefox 2.0.0.12 is that they made some js changes like the 'keypress' event only handles the function keys but 'keydown' works and the characters returned are all uppercase now.

looks like this widescreen toggle is broken in 2.0.0.12 I'm fixing it now

I'm not a big fan of hiding the actions bar, but I could see it would be useful in hiding it for items other than the one with id = current-entry. I'll take a look at doing that. I'm having a little trouble getting the css to say display:inline when I have div class="entry-actions" under div id="current-entry" any ideas?

as for the border, I'm undecided as it does change the look quite a bit and you only gain in having more entries on the screen not by being able to read more of any given entry. I find mine feeds are longer posts so maybe thats why it doesn't bug me.

as for the red line in firefox 3 I'll give that a look.