[Bug 23589] Endangered Features : output

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23589

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #6 from Robin Berjon <robin@w3.org> ---
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: Rejected
Change Description: none
Rationale:
First and foremost Anthony, I would like to say that I heartily agree with your
approach and feelings. I personally have a strong love for this sort of "small"
feature that actually does nice things without being particularly bloggable.

However, we are planning on shipping HTML 5.0 this year. The rules for what
goes into that draft are clear: it has to be (sufficiently) implemented. The At
Risk list is basically just a listing of things that look like they may not
make the cut. But the goal there isn't to push them out of the draft, but
rather to bring attention to them.

We will revisit this list in the coming few months, probably inside of Q2. It's
not at all cast in stone. The most important criterion there will be testing.
If there's a test that shows a feature is supported, then it very likely just
stays in. If your passion for this continues, I invite you to look at
https://github.com/w3c/web-platform-tests/ as well as the community that goes
with, and if there are no tests for a feature you care about then contribute
some.

Beyond that, the only way of making sure that one of those features makes the
5.0 cut (those that don't will stay in 5.1) is implementation. You can file
bugs with implementers (or register your support with existing bugs), or, if
you have the time and skills, maybe even contribute.

For the time being however, the At Risk list stays the same, pending the
upcoming re-evaluation.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 21 January 2014 17:17:05 UTC