Change <input type="file"> filename encoding in multipart/form-data uploads in forms with non-Unicode accept-charset to use HTML numeric character references rather than '?' when a filename the user selects contains characters not representable in the target character encoding. This change would align our behavior with the existing behavior of Firefox and Edge. It is hoped that this behavior can eventually achieve cross-browser consensus and standardization.

Documentation

• https://github.com/whatwg/html/issues/3223
• https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#multipart-form-data
• https://encoding.spec.whatwg.org/#concept-encoding-process
• https://tools.ietf.org/html/rfc7578#section-4.2
• https://tools.ietf.org/html/rfc5987#section-3.2

Status in Chromium

Blink components: Blink>Forms

Implementation status: Enabled by default (tracking bug)

Consensus & Standardization

• Firefox: Shipped/Shipping
• Safari: No signal
• Web Developers: No signals

Owner

• bsittler@chromium.org

Comments

From https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#multipart-form-data : "File names included in the generated multipart/form-data resource (as part of file fields) must use the character encoding selected above, though the precise name may be approximated if necessary (e.g. newlines could be removed from file names, quotes could be changed to "%22", and characters not expressible in the selected character encoding could be replaced by other characters)."

Last updated on 2021-03-09