[GH-ISSUE #1546] Autocorrect and Autocapitalize enabled for wifi "Password" field on WiFi setup page #1320

New issue

Open

opened 2026-02-28 01:29:34 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 01:29:34 +03:00

Owner

Originally created by @pomplesiegel on GitHub (Jan 11, 2023).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1546

Currently a browser will try to autocorrect the value a user enters for the wifi password, because of HTML settings. This is because there are no fields autocorrect="off" and autocapitalize="none" for passwords.

Current HTML for password field:
<input id="p" name="p" maxlength="64" type="password" placeholder="">

In contrast, the SSID field has both of these in place correctly:
<input id="s" name="s" maxlength="32" autocorrect="off" autocapitalize="none" placeholder="">

Is there an easy way to add this into the password's HTML using the current API? I imagine autocorrect="off" and autocapitalize="none" should always be in place, since passwords are often not proper english words.

Thank you,
Michael

Originally created by @pomplesiegel on GitHub (Jan 11, 2023). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1546 Currently a browser will try to autocorrect the value a user enters for the wifi password, because of HTML settings. This is because there are no fields `autocorrect="off"` and `autocapitalize="none"` for passwords. Current HTML for password field: ```<input id="p" name="p" maxlength="64" type="password" placeholder="">``` In contrast, the SSID field has both of these in place correctly: ```<input id="s" name="s" maxlength="32" autocorrect="off" autocapitalize="none" placeholder="">``` Is there an easy way to add this into the password's HTML using the current API? I imagine `autocorrect="off"` and `autocapitalize="none"` should always be in place, since passwords are often not proper english words. Thank you, Michael

kerem commented

2026-02-28 01:29:35 +03:00

Author

Owner

@tablatronix commented on GitHub (Jan 13, 2023):

shouldn't this be the default for browsers on input type=password?

@tablatronix commented on GitHub (Jan 13, 2023): shouldn't this be the default for browsers on input type=password?

kerem commented

2026-02-28 01:29:35 +03:00

Author

Owner

@pomplesiegel commented on GitHub (Jan 13, 2023):

Interesting! For whatever reason at least through the "safari" browser on Mac OS desktop it still attempted to create multiple capitalized words out of my password input. Are you seeing a different behavior on your browser?

@pomplesiegel commented on GitHub (Jan 13, 2023): Interesting! For whatever reason at least through the "safari" browser on Mac OS desktop it still attempted to create multiple capitalized words out of my password input. Are you seeing a different behavior on your browser?

kerem commented

2026-02-28 01:29:35 +03:00

Author

Owner

@tablatronix commented on GitHub (Jan 13, 2023):

I can check, but we can add that just to be sure I guess, it just takes memory

@tablatronix commented on GitHub (Jan 13, 2023): I can check, but we can add that just to be sure I guess, it just takes memory