- From: Daniel Buchner <notifications@github.com>
- Date: Sat, 18 Feb 2017 22:21:37 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 19 February 2017 06:22:11 UTC
@oleersoy good idea, let's talk simple examples - namely, brass tacks product requirements - and craft a solution that fits: - Extension of natives should be possible, and use common code mechanisms (classes, attributes, etc.) - An extended native should be recognizably, visually associated with its base element in HTML and CSS source - Extending natives should be a simple addition to a Custom Element declaration/definition I'm still reading through material, but let me know if there is a proposed solution that checks these boxes. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/509#issuecomment-280899274
Received on Sunday, 19 February 2017 06:22:11 UTC