Input elements with autocomplete="off" can still show an autocomplete

Not reproducible Issue #7526530

Details

Author
Philip W.
Created
May 11, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

It seems like autocomplete="off" for an input element still let the input element show an autocomplete, if the autocomplete suggestions have been entered in another control with autocomplete enabled. This is causing problems for us, as we have third party component which use input elements in their implementations without possiblity to set id or name to indentify the input.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

    • Hello,

      Thanks for the feedback on Edge. I am not able to repro this as you have described. I setup a repro here:

      http://jsbin.com/cudinesago/edit?html,css,js,output

      Please feel free to edit the sample and update us with the code that demonstrates the problem.

      All the best,
      The MS Edge Team

    • I tried reproducing the behavior outside of our product, but it wasn’t as simple as I thought. I can still get autocomplete suggestion for an input field with autocomplete="off" in our product, but I cant seem to add to that list of suggestions. Also, the problem seem to have disappeared in some cases for input fields in our product, maybe there has been some changes how autocomplete is handled recently in a update for Edge? We have cleared the form cache in Edge now to see if/when autocomplete options are added to the input field.

    • To my knowledge there has not been any changes pushed to Edge regarding autocomplete.  Do you have any way that you can provide us access to the product you are experiencing these issues with?

      We would be happy to look into this with more detail.  Please e-mail login details to v-bredw@microsoft.com should you wish to disclose these details.

    • We have been unable to reproduce the problem since we cleared the cache in Edge. I guess there’s no point to continue with this further unless we encounter the problem again. I will come back and reopen the issue or create a new one if we are able to reproduce the problem in the future, but for now we might as well close it I guess.

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • Okay, will close it out.  Should it happen again feel free to open a new issue - we will happily investigate.

    You need to sign in to your Microsoft account to add a comment.

    Sign in