Comment #16 on issue 151 by nolongerunknown: JSSM history manager behaves
differently in Chrome
http://code.google.com/p/chromium/issues/detail?id=151
I've distilled this down to demonstrate exactly what the difference is:
navigation-related events are handled differently in Chrome.
The file
Comment #17 on issue 151 by nolongerunknown: JSSM history manager behaves
differently in Chrome
http://code.google.com/p/chromium/issues/detail?id=151
Also, in light of the discovery of the root issue, the title of this bug
should
probably be adjusted accordingly.
--
You received this mess
Issue 151: JSSM history manager behaves differently in Chrome
http://code.google.com/p/chromium/issues/detail?id=151
Comment #15 by [EMAIL PROTECTED]:
This page doesn't provide any details on what's expected to happen, so I
have no way
of evaluating the bug:
http://nathanhammond.com/jssmsource
Issue 151: JSSM history manager behaves differently in Chrome
http://code.google.com/p/chromium/issues/detail?id=151
Comment #14 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Status: Untriaged
Owner: ---
--
You received this message b
Issue 151: JSSM history manager behaves differently in Chrome
http://code.google.com/p/chromium/issues/detail?id=151
Comment #13 by nolongerunknown:
Ojan, I'm going to try and distill this a bit farther, I've seen both
behaviors (but
never with it working in JSSM or RSH).
I think it may have t
Issue 151: JSSM history manager behaves differently in Chrome
http://code.google.com/p/chromium/issues/detail?id=151
Comment #12 by [EMAIL PROTECTED]:
nolongerunknown: I don't see what the bug is. Your test page seems to work
the same
to me in Chrome and Firefox. Can you describe what the expec
