W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2012

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 27 Nov 2012 15:48:53 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-12543-2486-6fOxK6GDKC@http.www.w3.org/Bugs/Public/>

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
                 CC|                            |robin@w3.org
          Component|LC1 HTML5 spec              |default
            Product|HTML WG                     |HTML.next

--- Comment #17 from Robin Berjon <robin@w3.org> ---
I'm moving this to .next because:

• It won't be addressed before CR;
• It's probably too big of a change to address in CR;
• While not specified in an optimal manner, the behaviour appears to be
supported by all browsers save one and so is widespread (user questions on
StackOverflow show that it does lead to interop issues);
• The slated replacement for this section (Anne's URL spec) maintains this

So all in all, removing this text now would do more harm than good, and would
be less in line with reality than including it, even if it is imperfect. This
doesn't mean we're giving up on perfection: that's what .next is for.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 27 November 2012 15:49:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:35 UTC