Open
Bug 1273716
Opened 10 years ago
Updated 4 years ago
Consider implementing write-only <input> support
Categories
(Core :: DOM: Security, enhancement, P5)
Core
DOM: Security
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | affected |
People
(Reporter: MattN, Unassigned)
References
()
Details
(Whiteboard: [domsecurity-backlog])
Either via CSP and/or an attribute on a <input> or <form>, we should provide a way for authors to prevent page access to sensitive form field values such as credit card and password ones to prevent leaks to attackers.
Proposal email: https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Oct/0181.html
Draft spec: https://mikewest.github.io/credentialmanagement/writeonly/
| Reporter | ||
Comment 1•10 years ago
|
||
I think support for <input writeonly> would be a fine first-step if we want to reduce the scope of what's in the current draft since it's the most common element used for these types of sensitive fields.
| Reporter | ||
Comment 2•10 years ago
|
||
A simple way to help drive adoption would be to add developer console warnings when type=password or autocomplete=cc-number/cc-csc/current-password/new-password fields are lacking @writeonly.
Updated•10 years ago
|
Priority: -- → P5
Whiteboard: [domsecurity-backlog]
Updated•4 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•