RE: Apple's updated feedback on Custom Elements and Shadow DOM from Domenic Denicola on 2015-07-21 (public-webapps@w3.org from July to September 2015)

From: Domenic Denicola <d@domenic.me>
Date: Tue, 21 Jul 2015 05:29:58 +0000
To: Maciej Stachowiak <mjs@apple.com>, public-webapps <public-webapps@w3.org>
Message-ID: <CY1PR0501MB13690CD2A2ECBC32F2971C85DF840@CY1PR0501MB1369.namprd05.prod.outlook.>

Thanks very much for your feedback Maciej! I know we'll be talking a lot more tomorrow, but one point in particular confused me:

From: Maciej Stachowiak [mailto:mjs@apple.com] 

> 4. Specifically, we don't really like the "Optional Upgrades, Optional Constructors" proposal (seems like it's the worst of both worlds in terms of complexity and weirdness) or the "Parser-Created Classes" proposal (not clear how this even solves the problem).

Specifically with regard to the latter, what is unclear about how it solves the problem? It completely gets rid of upgrades, which I thought you would be in favor of.

The former is, as you noted, a compromise solution, that brings in the best of both worlds (from some perspectives) and the worst of them (from others).

Received on Tuesday, 21 July 2015 05:30:37 UTC