[chromium-bugs] Issue 151 in chromium: Lack of back/foward cache causes different history behavior

Comment #22 on issue 151 by nstoertz: Lack of back/foward cache causes different history behavior http://code.google.com/p/chromium/issues/detail?id=151 See bug 5353 for what looks to be a good repo case of this problem: http://code.google.com/p/chromium/issues/detail?id=5353 -- You received

[chromium-bugs] Issue 151 in chromium: Lack of back/foward cache causes different history behavior

Comment #21 on issue 151 by nolongerunknown: Lack of back/foward cache causes different history behavior http://code.google.com/p/chromium/issues/detail?id=151 So, I'm wrong about this being wrapped up. While double-checking my tests I saw the same original symptom: the failure of form field

[chromium-bugs] Issue 151 in chromium: Lack of back/foward cache causes different history behavior

Updates: Status: Fixed Comment #20 on issue 151 by o...@chromium.org: Lack of back/foward cache causes different history behavior http://code.google.com/p/chromium/issues/detail?id=151 Ah. That's great. Thanks for the update and thanks for following up on this bug with a good testcas

[chromium-bugs] Issue 151 in chromium: Lack of back/foward cache causes different history behavior

Comment #19 on issue 151 by nolongerunknown: Lack of back/foward cache causes different history behavior http://code.google.com/p/chromium/issues/detail?id=151 The version I reported this in was triggering DOMContentLoaded twice upon revisiting the page: once before the inline function was c

[chromium-bugs] Issue 151 in chromium: Lack of back/foward cache causes different history behavior

Updates: Summary: Lack of back/foward cache causes different history behavior Cc: da...@chromium.org bre...@chromium.org Comment #18 on issue 151 by o...@chromium.org: Lack of back/foward cache causes different history behavior http://code.google.com/p/chromium/issues/detail?id=