input hidden does not cache value
Reported by
pro100....@gmail.com,
Aug 11 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. change value of hidden input 2. go to another page 3. press back button and hidden input value will be initial What is the expected behavior? hidden input must to contain changed value What went wrong? Value of hidden input has to be cached by browser and when you come back by browser back button it should contain changed value Did this work before? Yes 59 Chrome version: 60.0.3112.90 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Aug 14 2017
reporter@ Could you please provide us a sample site/url to reproduce the issue so that it would help us in triaging the issue better. Thanks!!
,
Aug 14 2017
You can reproduce this bug by openning attaeched files with instractions
,
Aug 14 2017
Thank you for providing more feedback. Adding requester "jbanavatu@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 17 2017
Able to reproduce the issue on the latest stable(61.0.3163.100) and the latest canary(64.0.3242.0) on Windows-10, Mac OS 10.12.6 and Linux Ubuntu 14.04. Regressed in M-60: Last good build: 60.0.3100.0 First bad build: 60.0.3101.0 Changelog: ========== https://chromium.googlesource.com/chromium/src/+log/60.0.3100.0..60.0.3101.0?pretty=fuller&n=10000 Suspecting: https://codereview.chromium.org/2879063003. As per the chromium update, seeing 'no bugs to be assigned to tkent@', hence assigning to keishi@ as the reviewer of the CL. Note: Facing issue with the bisect script for the above range on Windows and Mac.
,
Oct 17 2017
This is the intended behavior after https://codereview.chromium.org/2879063003 As discussed in crbug.com/651822, restoration of hidden inputs was inconsistent/flaky for all browsers. We chose to stop saving/restoring values of input[type=hidden] in order to guarantee consistent/predictable behavior for JS authors. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by manoranj...@chromium.org
, Aug 11 2017