W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10806] ignoring escapes is not needed for compatibility with existing content

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 08:23:13 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P1EQ5-00061Q-7T@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10806

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |mjs@apple.com
         Resolution|                            |WONTFIX

--- Comment #10 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-30 08:23:12 UTC ---
Upon further investigation, it turns out WebKit has changed behaviour. It used
to ignore all punctuation (it didn't support backslash escapes, just ignored
punctuation like Opera). Newer trunk builds however now don't ignore
punctuation.

(In reply to comment #7)
> 2) The question of *why* Opera is handling the escapes properly isn't really
> relevant; what counts is the observable behavior.

The point is that Opera isn't handling the escapes at all. For example, if you
put a backslash before the final quote, it doesn't continue the string. It
still ends at the quote. For example, consider:

   http://www.hixie.ch/tests/adhoc/html/parsing/encoding/122.html
   http://www.hixie.ch/tests/adhoc/html/parsing/encoding/123.html


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: Rejected
Change Description: no spec change
Rationale: As far as I can tell, no browsers with more than 1% market share do
anything with backslashes at all, and the browsers that ignored backslashes are
actively moving towards what the spec says.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 30 September 2010 08:23:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC