W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2015

RE: Custom elements contentious bits

From: Domenic Denicola <d@domenic.me>
Date: Sun, 6 Dec 2015 22:17:49 +0000
To: Dylan Barrell <dylan.barrell@deque.com>
CC: public-webapps <public-webapps@w3.org>
Message-ID: <CY1PR0501MB13691B083D6136AC1377AF78DF0A0@CY1PR0501MB1369.namprd05.prod.outlook.com>
Shadow DOM and custom elements are different features. You may have had better luck bringing that up at the shadow DOM meeting which already happened several months ago.

From: Dylan Barrell [mailto:dylan.barrell@deque.com]
Sent: Sunday, December 6, 2015 17:17
To: Domenic Denicola <d@domenic.me>
Cc: public-webapps <public-webapps@w3.org>
Subject: Re: Custom elements contentious bits

Domenic,

Closed shadow DOM and its impact on test automation and auditing is also a very important issue.

--Dylan


On Wed, Nov 25, 2015 at 3:16 PM, Domenic Denicola <d@domenic.me<mailto:d@domenic.me>> wrote:
Hi all,

A bit ago Jan put together an initial draft of the "contentious bits" for custom elements, in preparation for our January F2F. Today I went through and expanded on the issues he put together, with the result at https://github.com/w3c/webcomponents/wiki/Custom-Elements:-Contentious-Bits. It morphed into a kind of agenda for the meeting, containing "Previously contentious bits", "Contentious bits", "Other things to work out", and "Other issues worth mentioning".

It would be lovely if other vendors could take a look, and fill in anything they think is missing, or correct any inaccuracies.

Over all I'm pretty optimistic that we've narrowed this down to a small set of issues and will be able to make progress at the F2F.



--
Download FireEyes Free: http://getfireeyes.com/

Life is ten percent what happens to you and ninety percent how you respond to it. - Lou Holtz

Received on Sunday, 6 December 2015 22:18:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:58 UTC