- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Oct 2012 12:04:17 +0000
- To: public-html-bugzilla@w3.org
- Message-ID: <bug-16166-2486-BoYKmB88EI@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16166 --- Comment #14 from Robin Berjon <robin@w3.org> --- (In reply to comment #13) > Ok. I guess my question comes down to "what does 'keep working on this' mean > in practical terms?" Reach consensus on a solution, have the editors add it to the spec. Business as usual! > If I understand correctly, 'rejected' only applies in the context of HTML5 That's correct — as per the WG decision policy, pushing a bug to be resolved later is "Rejected" but only for HTML5. It's not rejected for future versions (I do find this confusing, I would rather we said "Deferred" or some such). > but doesn't imply that the bug is closed, and the bug keeps its status of > 'new' under HTML.next product - and that therefore we keep adding any > comments to this bug and look for a response here at some point from the > HTML.next editor. Is that right? Yes indeed, please keep providing all the input needed to solve these issues for all bugs moved to HTML.next. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 16 October 2012 12:04:23 UTC