No evidence either way. Given we've had non-compat parameter defaults for a
while, your worry is legit. We'll deal with web compat issues with JS as it
comes up -- unfortunately the reality is that until we ship something, we
have very little idea if it's breaking.
On Fri, Oct 7, 2016 at 8:14 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com>
wrote:
> On 2016-10-07 8:01 AM, Tom Schuster wrote:
> > To simplify parsing ES 2016 disallows "use strict" in functions with
> > non-simple parameters, like defaults or rest.
> >
> > For example `function f(a = 1) { "use strict"; }` is going to start
> > throwing.
> >
> > Chrome, JSC and Edge already made this change.
>
> Do we have any evidence to suggest that making this change doesn't break
> webpages in Gecko, if they're using browser sniffing to parse code that
> they don't parse in other engines?
>
> Thanks,
> Ehsan
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
--
shu
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
