Remove isomorphic decoding of URL fragment identifier (removed)

When Chrome opens a URL with a fragment id, it decodes %xx and applies isomorphic-decode [1] to it, then tries to find an element with the decoding result as an ID in some cases. No other browsers do this, and it's not defined by the standard. For example, if a user opens example.com/#%F8%C0, Chrome 1. searches the page for an element with id="%F8%C0" 2. If it’s not found, it searches the page for an element with id="øÀ" [1] https://infra.spec.whatwg.org/#isomorphic-decode

Specification

De-facto standard

Status in Chromium

Blink>HTML


Removed (tracking bug) in:

  • Chrome for desktop release 73
  • Chrome for Android release 73
  • Android WebView release 73
  • Opera release 60
  • Opera for Android release 60

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Shipped
  • Shipped
  • Shipped
  • No signals

Owner

Last updated on 2019-02-04