- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Mar 2012 21:59:35 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16292
Summary: conflation of DOMString and deflated DOMString
Product: WebAppsWG
Version: unspecified
Platform: All
URL: http://dvcs.w3.org/hg/xhr/raw-file/8d4e9ccfdbd4/Overvi
ew.html
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: XHR
AssignedTo: annevk@opera.com
ReportedBy: glenn@skynav.com
QAContact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
In section 4.7.1., step 2 states "let method be the result of deflating
method". This statement is not well defined since method is a DOMString (a
16-bit coding unit sequence) and the results of deflating method is an 8-bit
(byte) sequence.
Furthermore, step 3 states "if method is a case-insensitive match for CONNECT,
DELETE, GET, HEAD, OPTIONS, POST, PUT, TRACE, or TRACK subtract 0x20 from each
byte...". Here, "method" is obviously being interpreted as a byte sequence (a
deflated DOMString) but in contravention of its declared type (DOMString).
Moreover, the rule talks about a "case-insensitive match for CONNECT, ...", but
these strings "CONNECT", etc., are presumably interpreted as DOMStrings, since
that is the only string type being used.
The same problem occurs under 4.7.2 steps 2, 3, and 4.
--
Configure bugmail: https://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 Friday, 9 March 2012 21:59:37 UTC