[Bug 11613] At step 6 - for an empty Token, all the space characters will be removed then what is being added at Step 7 and how the empty string is getting counted ?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11613

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |NEEDSINFO
            Summary|At setp 6 - for an empty    |At step 6 - for an empty
                   |Token, all the space        |Token, all the space
                   |characters will be removed  |characters will be removed
                   |then what is being added at |then what is being added at
                   |Setp 7 and how the empty    |Step 7 and how the empty
                   |string is getting counted ? |string is getting counted ?

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-24 19:48:14 UTC ---
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: Did Not Understand Request
Change Description: no spec change
Rationale: If the question is "what does step 6 add when /s/ is the empty
string" then the answer is "the empty string". I don't see the problem here.
Could you elaborate?

-- 
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 Monday, 24 January 2011 19:48:16 UTC