New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 729519 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Non-Regression: Blank result section is seen on back navigation in w3schools.com

Project Member Reported by sc00335...@techmahindra.com, Jun 5 2017

Issue description

Chrome Version: 59.0.3071.86 
OS: Ubuntu 14.04,Windows

What steps will reproduce the problem?
(1)Launch chrome and go to https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_form_submit ,observe results section >> Hit Submit button 
(2)Now click on back navigation button and observe results section

Expected: On hitting back button some results should be seen.
Actual: Instead blank results section is seen.

This is a Non-regression issue seen from M36 series

Same works fine in Firefox.

 
Actual_w3schools.ogv
2.0 MB View Download
Labels: OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.12.4 using chrome version 59.0.3071.86 

Comment 2 by creis@chromium.org, Jun 6 2017

Cc: clamy@chromium.org nasko@chromium.org
Owner: creis@chromium.org
Status: WontFix (was: Untriaged)
I think this is working as intended.

This page creates an about:blank iframe called "iframeResult".  As the main frame loads, it calls a JavaScript function (submitTryIt()) which uses document.write to inject the contents of the code form on the left into the iframeResult iframe.

This means there's no actual URL corresponding to the form you see when you load the page.  (It's just about:blank, with content injected via script.)  Therefore, when you go back, it loads about:blank again.  You can get the content back if you click the green Run button.

Firefox has a back/forward cache which may explain the behavior you see there.  I notice that Firefox doesn't handle the case that you close the tab and re-open it when viewing the "Submitted Form Data" page in the iframe-- it loads the original form instead.

Anyway, unless/until we add a back/forward cache (which is a massive undertaking), I don't think there's much to change here.

Sign in to add a comment