- From: <bugzilla@jessica.w3.org>
- Date: Sun, 21 Jul 2013 00:52:31 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22745 Bug ID: 22745 Summary: [Custom]: Use case for registering a type extension of an unknown element Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: dominicc@chromium.org QA Contact: public-webapps-bugzilla@w3.org Blocks: 14968 Here is an interesting use case for the 'extends' attribute: polyfilling a HTML element that is not implemented yet by registering a type extension of an unknown element For example, say a UA implements Custom Elements but not <dialog>. It is neat that Custom Elements can be used to polyfill <dialog> with <dialog is="polyfill-dialog">. This gives polyfills a very smooth upgrade path--they can detect if there's a native HTMLDialogElement and flip to being a no-op. Maybe the Explainer could incorporate this use case; WDYT? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 21 July 2013 00:52:33 UTC