12059 2011-02-14 10:29:02 +0000 new normative ref to DOMRANGE 2011-09-06 20:06:59 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows NT RESOLVED FIXED http://dev.w3.org/html5/spec/Overview.html#refsDOMRANGE P2 normal --- 1 julian.reschke ian ayg ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 45467 0 julian.reschke 2011-02-14 10:29:02 +0000 Since the last WD, the spec has gained a new normative reference to DOMRANGE - is there an associated bug related to this? Any discussion on the mailing list? Also, the referenced document says: "I do not intend to finish this specification. Please go ahead and fork if you'd like to work on it." Is this supposed to go into the Last Call draft? 45635 1 ayg 2011-02-16 00:10:50 +0000 AFAIK, the plan is that DOM Range should be submitted as an Editor's Draft to the Web Apps WG fairly soon. Are there any problems with going to Last Call with normative dependencies on less complete specs? CSS 3 Selectors is PR, but it has a normative dependency on CSS 2.1, which is WD. 47886 2 ian 2011-05-03 19:54:02 +0000 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: Bug doesn't seem to describe a bug. 47930 3 julian.reschke 2011-05-04 08:10:44 +0000 Explanation why this is a problem: adding normative references to things that are early drafts is a problem when trying to get to Last Call. That being said: as of today, the spec doesn't use the reference anyway. Please remove it. 48003 4 ian 2011-05-04 23:35:45 +0000 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. 48004 5 contributor 2011-05-04 23:36:20 +0000 Checked in as WHATWG revision r6071. Check-in comment: make a reference vanish from the w3c copy http://html5.org/tools/web-apps-tracker?from=6070&to=6071 48053 6 julian.reschke 2011-05-05 07:17:56 +0000 Thanks. Out of curiosity: why is the ref staying in the WhatWG version when it's not used? 53953 7 mike 2011-08-04 05:34:48 +0000 mass-move component to LC1 56445 8 julian.reschke 2011-09-06 20:06:59 +0000 See also <http://www.w3.org/Bugs/Public/show_bug.cgi?id=14029>