Recently active topics in Fluid tagged with google reader

I've noticed that when using the Google Reader the up and down arrows and page-up and page-down keys don't act the way they're supposed to.

It seems that the problem stems from the fact that with most browsers, if javascript intercepts the event and squelches it, the event does not get processed by the browser chrome.

I was able to replicate this by going to: http://webonweboff.com/tips/js/event_...

If you scroll to the bottom it contains a text box you can use to find keycodes. If you hit "page-up" in Fluid, it scrolls up. If you hit "page-up" in Camino, it does not.

I just started using Fluid for Google Reader and I'm having problems with some keyboard shortcuts. Everything works, but certain shortcuts cause a system alert ("boink" noise, screen flash). j/k works. n/p works. But hitting 'return' in list view makes a system alert. Same thing with 'g' (the first key in g-u or g-h). The shortcuts still cause their desired effect, but the alerts are annoying.

Is there something I'm doing wrong? Can anyone else replicate this?

Google Reader runned under fluid does not use its setting Settings/Preferences/Start Page.

Scenario to reproduce:
1) Create label "work-safe" and put some rss feed into it.
2) Set Start Page to "work-safe"
3) Open Google Reader using fluid
4) Switch view to "All items"
5) Exit from Google Reader
6) Open Google Reader again

I suppose, that:
Google Reader shoud be open with "work-safe" label

But in reality it:
Google Reader opens with "All items" tab

I suppose, that I am right and not fluid cause:
In Safari, Firefox and Internet Explorer it were working fine

It is definitely bothers me, cause in previous I used Safari and all things were working fine.

Seems that the unread count for Google Reader is rarely correct. Is this updated on a configurable timer?