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 called, and once after. I suppose I should have mentioned that. Before testing it again today I updated to the most recent version and that issue has disappeared from my simple test case. As to the lack of a back-forward cache it shouldn't affect compatibility since everybody already has to code for IE. Issue 2879 is an already-assigned feature request for back-forward caching. By my opinion, this issue can be closed. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
