> The 'input-security' property may be used by authors to enable or disable this obscuring. Hmm, why the CSS author should be involved in that? Isn't the problem here that we haven't implemented bug 502258? (a built-in button inside the password field that the *user* can click on the show the password text) It seems to me that the user should be in control of this, not the CSS author.
Bug 1735384 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> The 'input-security' property may be used by authors to enable or disable this obscuring. Hmm, why should the CSS author should be involved in that? Isn't the problem here that we haven't implemented bug 502258? (a built-in button inside the password field that the *user* can click on the show the password text) It seems to me that the user should be in control of this, not the CSS author.
> The 'input-security' property may be used by authors to enable or disable this obscuring. Hmm, why should the CSS author be involved in that? Isn't the problem here that we haven't implemented bug 502258? (a built-in button inside the password field that the *user* can click on the show the password text) It seems to me that the user should be in control of this, not the CSS author.