Closed GoogleCodeExporter closed 8 years ago
Again, can't replicate the issue.
Are you using the keyboard shortcut or clicking?
Are you getting any JS errors? Tools > JavaScript Console > Errors
Original comment by anst...@gmail.com
on 21 Nov 2011 at 2:43
Attached a screenshot of the JS errors. Hope you can make sense of it/hope it
helps.
And umm, what happens btw is that pressing (v) opens the item in the
foreground, and not the background. Kind of how Reader works by default.
Same thing goes whether you have reader on a tab, or as an application shortcut.
Original comment by jethro.koon
on 21 Nov 2011 at 3:06
Attachments:
And oh, this works fine for the old version [Minimalist for Google Readerâ„¢
(DEPRECATED!)0.5.13]
Original comment by jethro.koon
on 21 Nov 2011 at 3:08
There are only two errors there, either related to MinEverything. Errors
related to this feature will be red and will appear in the console every time
you attempt to open an item with [ v ].
That screenshot was taken with Minimalist for Google Reader enabled. Having
both enabled might cause a conflict. Try disabling MinGreader and make sure
that the Greader module of MinEverything is enabled (the Minimalist icon turns
black when on the Google Reader page. There have been some module enable bugs
reported.)
Original comment by anst...@gmail.com
on 21 Nov 2011 at 3:12
My bad. (v) now works when you have Reader on a tab, but not when you have it
as an Application Shortcut. JS isn't bringing up errors.
Same issue again: The item is opening, but on the foreground and not in the
background.
Original comment by jethro.koon
on 21 Nov 2011 at 3:27
Attachments:
Oh okay, I'll do some testing while launched as an Application Shortcut before
the next release and see if I can figure out why it's acting different.
Original comment by anst...@gmail.com
on 21 Nov 2011 at 3:42
Original comment by anst...@gmail.com
on 21 Nov 2011 at 3:43
This issue appears to have disappeared when I re-installed the extension. Must
have been something on my end.
Original comment by jethro.koon
on 21 Nov 2011 at 6:06
Glad to hear it. I think Chrome may cache Application Shortcuts more
aggressively than most other pages.
Original comment by anst...@gmail.com
on 21 Nov 2011 at 6:20
Original issue reported on code.google.com by
jethro.koon
on 21 Nov 2011 at 1:46