--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAHixhFoprgS8z3ZE_TKJ%2BRFy%2BzKcfOZw%2BLbFOG%3DetzivpX6teg%40mail.gmail.com.
Good point. Is it worth splitting iOS and non-iOS cases?
On 14 June 2017 at 15:44, PhistucK <phis...@gmail.com> wrote:But can you use custom elements v1? Not all of the supported iOS versions support them (or ECMAScript 2015 classes).☆PhistucKOn Wed, Jun 14, 2017 at 9:00 AM, Adam Rice <ri...@chromium.org> wrote:'class' is listed under "Features To Be Discussed" in the "ES6 Support In Chromium" document, which means it's currently disallowed for Chromium code.
Custom elements v1, ie. the standardised version of custom elements, require the use of the ES6 class syntax. I think this makes the prohibition problematic.
I propose moving classes to the "Allowed Features" section.
----
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAHixhFoprgS8z3ZE_TKJ%2BRFy%2BzKcfOZw%2BLbFOG%3DetzivpX6teg%40mail.gmail.com.
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAHixhFoERPuvYeeAV%2BkVzTFu8N8O3v03q1ce4JRAnWRdwsN06A%40mail.gmail.com.
Note: you can like kinnnnda use ES5 classes. Are you trying to use Polymer or just vanilla custom elements?
Do you know which JS tools (closure compiler, clang-format, eslint, uglifyjs) work with class? Does it result in potential performance problems?
'class' is listed under "Features To Be Discussed" in the "ES6 Support In Chromium" document, which means it's currently disallowed for Chromium code.Custom elements v1, ie. the standardised version of custom elements, require the use of the ES6 class syntax.
I think this makes the prohibition problematic.I propose moving classes to the "Allowed Features" section.
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAHixhFoprgS8z3ZE_TKJ%2BRFy%2BzKcfOZw%2BLbFOG%3DetzivpX6teg%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAHnmYQ_XRyqnbi%3DKhSEJ%3DN9S4ea_babp%2Bju02%3DTgzETFu3cMSQ%40mail.gmail.com.
Yes, that is my understanding.On Jun 29, 2017 3:05 PM, "PhistucK" <phis...@gmail.com> wrote:I think classes are also supported everywhere customElements.define is at the moment as well?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAHnmYQ9pVECLrYPV3tQxxm2ppogm%3DP5mVV2PJpNqn93w%3D_NDCw%40mail.gmail.com.