25449 2014-04-24 23:04:01 +0000 Should we have a "masked" mode here? 2014-06-12 18:13:35 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#input-modalities:-the-inputmode-attribute P3 normal Unsorted 1 contributor ian ian manishearth mike contributor oldest_to_newest 104381 0 contributor 2014-04-24 23:04:01 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html Multipage: http://www.whatwg.org/C#input-modalities:-the-inputmode-attribute Complete: http://www.whatwg.org/c#input-modalities:-the-inputmode-attribute Referrer: Comment: Should we have a "masked" mode here? Posted from: 103.21.126.78 User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36 104385 1 manishearth 2014-04-24 23:07:18 +0000 See https://bugzilla.mozilla.org/show_bug.cgi?id=956906#c68 Since all major browsers now do not allow autocomplete=off on password fields, a small use case is left behind: when the website owner wishes to mask the typed characters (as a password box does), but does not want it to go through the password manager, i.e., the saved value is *not* a password. In such a case, `inputmode=masked` would be useful to tell the browser "please mask this input, but do not treat it as a password" 104625 2 ian 2014-04-28 23:26:54 +0000 Do you have an example? 105135 3 ian 2014-05-05 23:41:06 +0000 ping manishearth@gmail.com 105139 4 manishearth 2014-05-05 23:48:02 +0000 (In reply to Ian 'Hixie' Hickson from comment #3) > ping manishearth@gmail.com Sorry, thought I replied to this. No, I don't have an example -- the use case just came to mind whilst having the autocomplete discussion, and it seemed like something that would be nice to have. 105216 5 ian 2014-05-06 18:28:43 +0000 Ah, ok. If there's no compelling use case, I'd rather not add the feature. The browser vendors have enough on their plate already. 107745 6 ian 2014-06-12 18:13:35 +0000 Marking WONTFIX per comment 5. If a specific use case does come up, please don't hesitate to reopen the bug. I think the right solution isn't so much inputmode=masked, though, as returning to autocomplete=off, but with the browsers being a bit more moderate when deciding to ignore it (e.g. only deciding to ignore it if there's also a username field in the form, or some such). But either way, we'd have to be clear on why it would be bad for the UA to remember the value, even in the non-password case.