[chromium-dev] Re: history.back always fires onload in chromium - is it expected?

2009-11-05 Thread Tony Chang
It sounds like the test depends on the page cache being enabled so we won't be able to pass it until we support the page cache ( http://code.google.com/p/chromium/issues/detail?id=2879 ). There are a couple options: 1) Try to implement the page cache-- abarth probably has some thoughts on this.

[chromium-dev] Re: history.back always fires onload in chromium - is it expected?

2009-11-05 Thread Adam Barth
We might or might not decide to implement page cache (Darin is in the might not camp). In either case, this LayoutTest shouldn't drive that decision. Adam On Thu, Nov 5, 2009 at 12:17 PM, Tony Chang t...@chromium.org wrote: It sounds like the test depends on the page cache being enabled so

[chromium-dev] Re: history.back always fires onload in chromium - is it expected?

2009-11-05 Thread Kinuko Yasuda
Thanks for the replies, for now I'm going to do 2), i.e. mark the test SKIP, add a comment and wait for the decision for the page cache. (of course I don't think the test should determine the future of the page cache... :)) Kinuko On Fri, Nov 6, 2009 at 1:47 PM, Adam Barth aba...@chromium.org