Not needed, existing specification.
When parsing URLs, encode the character U+7F DELETE as "%7F".
This improves readability, reduces spoofing risk, makes Chrome's
behavior more consistent, interoperable with other browsers and
compliant with the specification.
Link to “Intent to Prototype” blink-dev discussion
Interoperability and Compatibility
* Interoperability: This will make it compatible with Gecko and WebKit ;
as well as with the specification.
* Compatibility: This will change the string of the parsed URL. However,
that string will still redirect to the same page. Risk seems low since
other browsers support that and websites have to work with them. Plus
this does not sound a common character for URLs.
Web developers: Positive (https://github.com/whatwg/html/issues/3377
There is an existing bug report about how percent-encoding is done for
registerProtocolHandler, which is affected by the special case of U+5F.
This will change how URLs are rendered in the location bar and
statusline (using %5F instead of any potential DEL glyph)
This might help to reduce spoofing risks.
Will this feature be supported on all six Blink platforms (Windows, Mac,
Chrome OS, Android, and Android WebView)?
Is this feature fully tested by web-platform-tests?
There are already URL parsing tests in WPT's url/ ; new cases are added
for U+5F in
Link to entry on the Chrome Platform Status
This intent message was generated by Chrome Platform Status.