W3C home > Mailing lists > Public > public-html@w3.org > April 2016

Re: HTML Features only in 0 or 1 browsers...

From: Chaals McCathie Nevile <chaals@yandex-team.ru>
Date: Sat, 16 Apr 2016 22:00:56 +0200
To: public-html@w3.org
Message-ID: <op.yf027ukjs7agh9@widsith.local>
Based on feedback received so far, and looking at our issues list, I'm  
trying to consolidate the information a bit - below is a full version

We'll need to raise a set of issues for the things that turn out not to be  
implemented - there is already a label for deprecating things in the  
github issues list.

On Wed, 06 Apr 2016 00:17:10 +0200, Travis Leithead  
<travis.leithead@microsoft.com> wrote:

> In our telecon today  
> (https://lists.w3.org/Archives/Public/public-html/2016Apr/0001.html), we  
> talked about enumerating a set of HTML 5.1 features that might not meet  
> a minimum bar for inclusion: are the implemented in at least 2 browsers?
> To answer this question, we turned to the API Catalog  
> (https://aka.ms/apicatalog) and filtered out the non-HTML 5.1 features.  
> The raw data used is attached (CSV file). We did a little spreadsheet  
> math to find columns where APIs were only supported in 0 or 1 browsers.  
> Here's the high-level summary:

Feature No browser supports:

These are all likely to be removed.

> Canvas Proxies
> dragexit
> table sorting

This already seems a strong candidate for removal, with an issue raised:  

> misc. <area> attributes (hreflang, type)
> autocomplete (textarea/select)
> ImageBitmap Factories
> force spell check
> misc. <input> props (valueHigh/valueLow)
> Content handler registration
> SVG root element global event handlers

Features at least 1 browser supports:
> Autocomplete Error event (Chrome)

Mozilla has a bug to implement this, but it shows no sign of happening.

> DataCue (Edge)

This is also implemented in webkit, but prefixed. Is there any sign that  
it will be unprefixed - or implemented more widely?

> Search Provider registration

> <dialog> (Chrome)

This *might* get implemented in Mozilla, as a counter to the effect of  
unshipping showModalDialog(), but it is a bit hard to read the bugzilla  
tealeaves from outside.

Anyone have real insight?

> Media Controller

This has one ongoing implementation (and various use cases) but looks like  
it won't get more so seems a candidate for removal. I plan to raise an  
issue. > <marquee> (Edge) (obsolete section)

This also works in Webkit, but we probably want to deprecate or remove it…

> <menuitem> (Chrome)

This also seems to work in Firefox as Ilya suggested.

> <style scoped> (Firefox)
> <textarea inputmode> (Chrome)

This looks like a candidate for testing in mobile browsers.

> minLength (textarea) (Chrome)
> location.assign (Edge)

This works in Webkit, and Firefox as well (modulo bugs)

> PromiseRejectionEvent (Chrome)
> RelatedEvent object (Chrome)
> ShowModalDialog (Safari)

Although this works it looks set to be obsoleted (like marquee).

> document.load (Firefox)

This one got more uptake:

> <details> (Chrome)

This is also in Webkit, and the functionality is set to release in FF  
soon. It also has apparent support from the DPub folks among others. I  
closed the issue about removing it, since it seems likely to stay.


Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Saturday, 16 April 2016 20:01:32 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:18 UTC