New issue
Advanced search Search tips

Issue 901015 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 900185
Owner:
Closed: Nov 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Autofill unable to be read by JS.

Reported by xaoti...@gmail.com, Nov 1

Issue description

Chrome Version       : 70.0.3538.77
OS Version: Kubuntu 18.10
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. Have multiple forms on a single page that have elements with the same name.  Ex. form 1 has "user" and form 2 has "user".
2. Use autofill, which appears to be filling multiple forms.
3. Attempt to read the value using Javascript.

What is the expected result?
JS's .value should return the autofilled value in a textbox.

What happens instead of that?
JS's .value returns a blank string.

Please provide any additional information below. Attach a screenshot if
possible.
This is happening on at least Windows and Linux.  I have recreated it on multiple computers, and have customers letting me know about it.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36



 
Labels: Needs-Feedback
Can you provide a reproduction URI? I've tried a simple site and the values appear correctly in input fields.
Labels: Needs-Triage-M70
I made a fiddle of the issue.  You can use Chrome's autofill on the second or third form, and you'll see it autofill the first form as well.  Along with that, the buttons will pull the value of the first name field, which only correctly pulls back for the first form.  The others will return an empty string as the value.

http://jsfiddle.net/pur5box6/
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 2

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: UI>Browser>Autofill
Labels: -Pri-3 Pri-2
Status: Untriaged (was: Unconfirmed)
Thanks very much for the reproduction.

This is definitely an issue with Autofill. I think it is because the UI display is getting displayed twice but not actually adjusting the fields in the second form.
Labels: RegressedIn-70 Target-71 FoundIn-70 Needs-Bisect
Thanks for the report. This is a regression in M70. I tested in M69 and the issue didn't happen. After updating the browser, I could reproduce it.

Adding labels to do a bisect.

More details on how to reproduce:
1. Go to http://jsfiddle.net/pur5box6/
2. On the bottom right of the screen, click on the first field of the second row.

The form in the first row is also filled, but only the second one was supposed to. 

I couldn't reproduce the issue in M72, so I think it has been fixed. However, it's a good idea to check if it's not happening in M71 as we still can merge a fix to the branch if needed.
Labels: OS-Mac
Cc: pbomm...@chromium.org
Labels: -Type-Bug -Pri-2 -Needs-Bisect Triaged-ET Target-70 Target-72 M-70 FoundIn-71 FoundIn-72 hasbisect OS-Windows Pri-1 Type-Bug-Regression
Owner: se...@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on chrome reported version# 70.0.3538.77 using Mac 10.12.6, Windows-10 and Ubuntu 17.10 by enabling #network-service flag from chrome://flags but unable to reproduce the issue using latest canary #72.0.3599.0, hence providing reverse bisect info:
Reverse Bisect Information:
=====================
Last Bad Build : 70.0.3538.93
First Good build: 71.0.3539.0

As the break is between branch and trunk builds, hence providing below manual change log from Omahaproxy
Change log: https://chromium.googlesource.com/chromium/src/+log/70.0.3538.0..71.0.3539.0?pretty=fuller&n=10000
Suspecting: https://chromium.googlesource.com/chromium/src/+/2e8a67679cecb521eee5e76d59d43f8792d08897 from above change log
Change-Id: I2d0d156108667d9463263f4e490761a506bf9a13
Reviewed-on: https://chromium-review.googlesource.com/1196924

Note: Able to reproduce the issue only by enabling the #network-service flag from chrome://flags on reported chrome version, with default/disabled chrome settings we are unable to reproduce the issue on chrome reported version, so not adding Release Blocker label to this issue.

@sebsg: Could you please check and merge the fix to M-70 if it is a valid candidate.

Thanks..!!
I'd very surprised if this was fixed by https://chromium.googlesource.com/chromium/src/+/2e8a67679cecb521eee5e76d59d43f8792d08897, as it's only changing the Settings page.

https://chromium.googlesource.com/chromium/src/+/97db05cb5fba6275bb9c6bd37d794722da801272/ seems more likely. We should try to merge it locally to the M70 branch to see if it fixes the issue.

M70 is currently at 100% stable. Is there any respin planned at this point?
And thanks krajshree@ for the bisect!
Cc: ftirelo@chromium.org
Mergedinto: 900185
Status: Duplicate (was: Assigned)
It seems to me this has the same root cause as 900185. Marking as duplicate.

Sign in to add a comment