- From: snuggs <notifications@github.com>
- Date: Thu, 11 Jan 2018 05:47:41 +0000 (UTC)
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/issues/69/356833120@github.com>
> the work would be useful for other things (such as MDN support tables, Intellisense data in browsers, etc.), - @dstorey For What It's Worth...currently there is an initiative mdn/browser-compat-data to better define the compat table with JSON data from Github. To be clear this is a fairly new initiative (i've been doing web components). Seems like the majority of momentum is around [HTML](https://github.com/snuggs/browser-compat-data/tree/master/html/elements) and [CSS](https://github.com/snuggs/browser-compat-data/tree/master/css). [Web APIs](https://github.com/snuggs/browser-compat-data/tree/master/api) very sparse. However, the intent is to have full coverage. I could be loading up a footgun as haven't done an assessment of what it would take to "complete the dom" to the liking of our requested needs but I know it will need to be done (eventually). Great idea (or at least better than updating a CMS via a WYSIWYG) nonetheless. And definitely should be brought to attention just for knowledge's sake. > This would require understanding each browsers feature flag system, right? - @wanderview With this strategy Feature Flags are *[Batteries Included](https://github.com/mdn/browser-compat-data/blame/a86e0b838d32c8dd12f7bea5a49df51fce6c3205/api/CustomElementRegistry.json#L29-L32). Thoughts.... /cc @domenic @annevk -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/69#issuecomment-356833120
Received on Thursday, 11 January 2018 05:48:04 UTC