Issue metadata
Sign in to add a comment
|
DevRel-SAP: Changed behavior of redirect
Reported by
orit.ha...@sap.com,
Sep 26 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: 1. Put the attached a.html and b.html in same directory 2. Launch a.html What is the expected behavior? Redirect to b.html What went wrong? a.html is launched. There is no redirect to b.html. Did this work before? Yes It works in Chrome 53 Chrome version: 54 beta Channel: beta OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Sep 26 2016
Already getting customer reports from the field.
,
Sep 26 2016
,
Sep 26 2016
,
Sep 26 2016
I can confirm that the issue exists in the current trunk build and that the stable release does the form submit as described. I don't see any errors in the console in the newer versions which would have made me believe this is something that we are blocking on person. Assigning Form>Submission and Navigation components for further investigation.
,
Sep 26 2016
This is an intentional behavior change. The current behavior matches to Firefox, Edge, and the HTML standard. https://chromium.googlesource.com/chromium/src/+/aaad992eef8e8c1e879f72afd9dabb05d3855e67
,
Sep 26 2016
,
Sep 26 2016
To clarify what you should do to make this code valid HTML again is to attach the cloned form to the document again. For example by adding document.body.appendChild(clonedForm); to your sample app before calling submit on the clonedForm object. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dskaram@chromium.org
, Sep 26 2016Labels: -Type-Bug -Pri-2 ReleaseBlock-Stable ReleaseBlock-Beta Pri-1 Type-Bug-Regression
Owner: blumberg@chromium.org