Not sure if this hack is still valid, but you could modify the tabindex property for that specific issue. This unfortunately leaves these items in the tab progression, which is not great for accessibility, and demonstrates how Google's attempts to override my decisions as the app developer is counter productive. This works for now, but I'm sure Google will make it needlessly hard again in a few weeks: I even tried changing the value to: autoComplete="Chrome, stop autofilling. None of the options on this page worked for me. Why is this still so hard to control in 2019 - what the heck Google?!
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |