- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Feb 2012 22:00:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14284
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #18 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-02-13 22:00:21 UTC ---
I don't understand what DOMParser needs. It doesn't have a byte stream at the
APIs you mention. As far as I can tell, it doesn't need this.
So since what the spec now has is sufficient for XHR, I'm closing this bug.
Please don't hesitate to reopen it or (better) file a new one if you need
anything else or if I misundersand DOMParser.
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: see diff given below
Rationale: Concurred with reporter's comments.
--
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 Monday, 13 February 2012 22:00:25 UTC