This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the current draft, section 2.2.1 appears the following: "In addition, user agents must implement the features defined in the DOM Range, DOM Parsing and Serialization, HTML Editing APIs, and UndoManager and DOM Transaction specifications that apply to their conformance class. [DOMRANGE] [DOMPARSING] [EDITING] [UNDO]" This requirement is not well formed since in no place is defined what "specifications ... apply to ... conformance class". In order to resolve this bug, either this paragraph must be removed, or a table (or equivalent) must be explicitly specified that enumerates which of each of these specifications are required for each defined conformance class.
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: I don't understand. Could you elaborate?
(In reply to comment #1) > 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: I don't understand. Could you elaborate? The cited language (still present in the current ED - Nov 4, 2011) states a normative requirement that UAs "implement the features defined in {...} specifications _that apply to their conformance class_." Nowhere in HTML5 is specified which features of {...} specifications apply to which conformance class. Therefore, this statement is not well defined, and is not interpretable for the purpose of conformance testing. For example, which features of "HTML Editing APIs" apply to the "Non-interacting presentation user agents" conformance class?