1. Start creating a homebrew monster, using Google Chrome with address autofill enabled.
2. Try to add a condition immunity.
3. Chrome thinks the condition immunity menu is a "state" field in an address form, and offers to autofill the user's state abbreviation, blocking the actual menu.
(Technical note: This appears to be Chrome's fault. Chrome has decided to not respect autocomplete="off". However, I was able to disable it by opening developer tools and putting a random string in the autocomplete property, e.g., autocomplete="stop-filling-in-this-field".)
I have the same issue but it also happens on the Saving Throw Proficiency field. Maybe if they renamed the fields to something else then Chrome won't try to fill them? E.g. instead of "state" it could be "con_imm"
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
How to reproduce:
1. Start creating a homebrew monster, using Google Chrome with address autofill enabled.
2. Try to add a condition immunity.
3. Chrome thinks the condition immunity menu is a "state" field in an address form, and offers to autofill the user's state abbreviation, blocking the actual menu.
(Technical note: This appears to be Chrome's fault. Chrome has decided to not respect autocomplete="off". However, I was able to disable it by opening developer tools and putting a random string in the autocomplete property, e.g., autocomplete="stop-filling-in-this-field".)
I have the same issue but it also happens on the Saving Throw Proficiency field. Maybe if they renamed the fields to something else then Chrome won't try to fill them? E.g. instead of "state" it could be "con_imm"