- From: Sam Ruby <rubys@intertwingly.net>
- Date: Sat, 12 Apr 2014 06:31:32 -0400
- To: public-html@w3.org
On 04/11/2014 09:41 PM, Silvia Pfeiffer wrote: > On Thu, Apr 10, 2014 at 11:47 PM, Paul Cotton <Paul.Cotton@microsoft.com> wrote: >> The HTML WG F2F meeting reviewed the HTML 5.0 CR [1] "at risk" features in >> preparation of publishing an HTML 5.0 heartbeat publication and eventually a >> Last Call with some material removed from the HTML 5.0 specification. This >> email is an attempt to summarize the recommendations of the F2F meeting. >> The definitive description of the discussions and recommendations is in the >> F2F minutes [2-3]. >> >> >> >> Bug 24812 was previously opened to cover the CR "at risk" features which >> were identified in the original HTML5 CR publication [1]: >> >> https://www.w3.org/Bugs/Public/show_bug.cgi?id=24812 >> >> This bug will eventually be updated with the recommendations of the meeting >> so that we have a definitive record of the results of the discussions and so >> that HTML WG members not at the F2F meeting can register their support or >> dissent on the recommended removals. >> >> >> >> First I will provide a summary of the HTML5 CR [1] "at risk" features and >> how the F2F meeting dealt with them. Note that the features that are >> removed from HTML 5.0 will be retained in HTML 5.1. >> >> >> >> HTML5 CR specification >> http://www.w3.org/TR/2014/CR-html5-20140204/ >> >> "The following features are at risk and may be removed due to lack of >> implementation. >> >> Application Cache - Do not remove >> <dialog> - Remove >> <details> and <summary> - Remove >> <input type=color> - Do not remove >> <input type=datetime>, <input type=month>, <input type=week>, <input >> type=time>, <input type=datetime-local> - Remove except for <input >> type=time> >> <output> - Do not remove >> <style scoped> - Remove >> <iframe seamless> - Remove >> Custom scheme and content handlers (registerProtocolHandler and >> registerContentHandler) - Do not remove (remove only >> isContentHandlerRegistered, isProtocolHandlerRegistered) >> Outline algorithm - Do not remove >> UA mechanism for navigating to resources linked to in cite="", see Bug 18915 >> for more. - Remove >> >> Second I will provide a modified list of the material that Robin proposed >> for items to be removed as discussed by the HTML WG F2F meeting: >> https://www.w3.org/html/wg/wiki/HTML5.0AtRiskFeatures#HTML_5.0_Features_at_Risk >> >> Features to remove in LC >> >> <details>/<summary> - From CR "at risk" features >> <dialog> - From CR "at risk" features >> :dir(), :valid, :invalid pseudoclass - Discussed at F2F meeting >> <iframe seamless> - From CR "at risk" features >> isContentHandlerRegistered, isProtocolHandlerRegistered - From CR "at risk" >> features >> input types datetime, datetime-local, week, month, time - From CR "at risk" >> features >> reportValidity - Discussed at F2F meeting >> <style scoped> - From CR "at risk" features >> XMLDocument.load - Discussed at F2F meeting (The Editors are considering if >> this should remain in HTML 5.1) >> >> Features at risk in LC >> >> DataCue - Discussed at F2F meeting >> :valid, :invalid (need to review >> http://www.w3c-test.org/html/semantics/selectors/pseudo-classes/valid-invalid.html) >> - Discussed at F2F meeting >> New ruby model - Discussed at F2F meeting >> HTMLMediaElement.addTextTrack - Discussed at F2F meeting > > I tried to find out from the minutes why addTextTrack is at risk, but > it was only mentioned without reasons. From http://www.w3.org/2014/04/09-html-wg-minutes.html : ... lots of failures on HTMLMediaElement.addTextTrack ... mostly failing at the moment > Could somebody please explain the reasons? > > Thanks, > Silvia. - Sam Ruby >> input type time - Discussed at F2F meeting >> >> /paulc >> >> >> >> [1] http://www.w3.org/TR/2014/CR-html5-20140204/ >> >> [2] http://www.w3.org/2014/04/08-html-wg-minutes.html >> >> [3] http://www.w3.org/2014/04/09-html-wg-minutes.html >> >> >> >> Paul Cotton, Microsoft Canada >> >> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 >> >> Tel: (425) 705-9596 Fax: (425) 936-7329 >> >> >> >> >> >> >> >> >
Received on Saturday, 12 April 2014 10:32:00 UTC