- From: Ryosuke Niwa <notifications@github.com>
- Date: Sat, 21 Jan 2017 18:14:28 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 22 January 2017 02:15:02 UTC
See https://github.com/w3c/webcomponents/issues/414#issuecomment-274183053 The question is why use symbols for this purpose? If we are worried about name conflicts, then that's kind of a moot point because we can't make existing framework-dependent component a custom element. There was also a school of thought that it's actually desirable for all classes defining a custom element to have the same set of methods instead of making them customizable. -- 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/414#issuecomment-274302606
Received on Sunday, 22 January 2017 02:15:02 UTC