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

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

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Tue, 5 Apr 2016 23:20:07 +0000
To: "weinig@apple.com" <weinig@apple.com>
CC: "public-html@w3.org" <public-html@w3.org>
Message-ID: <BY2PR0301MB1575DABE98100FA16B68FC0BF89E0@BY2PR0301MB1575.namprd03.prod.outlook.com>
Ah, good feedback. The API Catalog compares IDLs defined in specs with implementations, so there can be issues. One issue is that it looks strictly for the specified name, and does not consider implementation-specific prefixes (Moz/WebKit/MS). Thanks for the feedback. (Also, it looks like we took an old drop of Safari for the catalog, which has since added support for this.) So, promote MediaController from 0 browsers to 1 browser.

We’re working on open-sourcing the data mining routines, but it’s not quite ready yet. Thanks for your updates Sam.

From: weinig@apple.com [mailto:weinig@apple.com]
Sent: Tuesday, April 5, 2016 4:04 PM
To: Travis Leithead <travis.leithead@microsoft.com>
Cc: public-html@w3.org
Subject: Re: HTML Features only in 0 or 1 browsers...

Hi Travis,

How did you generate this API catalog, because, from a cursory look below, it doesn’t seem like you have things quite correct (I noted below where I think there are errors).  Is there a way others look at the methodology you used to generate the catalogue?

On Apr 5, 2016, at 3:17 PM, Travis Leithead <travis.leithead@microsoft.com<mailto: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:

No browser supports:
============
Canvas Proxies
dragexit
table sorting
misc. <area> attributes (hreflang, type)
autocomplete (textarea/select)
ImageBitmap Factories
force spell check
Media Controller

WebKit supports MediaController.


misc. <input> props (valueHigh/valueLow)
Content handler registration
SVG root element global event handlers

1 browser supports:

Autocomplete Error event (Chrome)
DataCue (Edge)

WebKit supports DataCue (as WebKitDataCue).


Search Provider registration
<details> (Chrome)

WebKit supports the <details> element.


<dialog> (Chrome)
<marquee> (Edge) (obsolete section)

WebKit supports the <marquee> element.


<menuitem> (Chrome)
<style scoped> (Firefox)
<textarea inputmode> (Chrome)
minLength (textarea) (Chrome)
location.assign (Edge)

WebKit supports location.assign.


PromiseRejectionEvent (Chrome)
RelatedEvent object (Chrome)
ShowModalDialog (Safari)
document.load (Firefox)

-Sam

Received on Tuesday, 5 April 2016 23:20:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 April 2016 23:20:39 UTC