[Bug 12543] [URL] Replacing backslash with forward slash in URIs doesn't seem to be necessitated by web compat

https://www.w3.org/Bugs/Public/show_bug.cgi?id=12543

Erika Doyle Navara <erika.doyle@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #22 from Erika Doyle Navara <erika.doyle@microsoft.com> ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:


   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: Adopted the WHATWG change to integrate with URL
specification (which omits the logic errors of the original URL parsing
algorithm outlined in HTML5)
Rationale: 

This was originally a LC1 bug which was won't fixed (Comment 13) in order for
discussion to continue in cloned WHATWG bug 15684, which was ultimately won't
fixed. In the meantime, Bug 14693, which points out a logical error in the URL
parsing algorithm, was duped to this bug. This bug was then reopened on the
grounds that it should not be resolved until the erroneous text of the
algorithm be removed and the logic ammended. The following commit merged from
the WHATWG spec does this and defers to the URL specification to define parsing
logic:

https://github.com/w3c/html/commit/b2e4d7e252df4c1be9e71666ec794ab0b2fa3a3e

Going forward, bugs in URL parsing should be filed on that spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 4 March 2013 23:52:05 UTC