Re: ES6 lexical temporal dead zone has landed on central

2014-09-18 Thread Philipp Kewisch
Is the AMO compatibility checker powerful enough to detect at least the first category of required changes? If so I don't think we should make any more special cases than needed. While the change is annoying for addon authors, in most cases the redeclaration is just an oversight and it would

Re: ES6 lexical temporal dead zone has landed on central

2014-09-18 Thread Bobby Holley
It would probably be easy for them to fix, yes. But we have a roughly fixed amount of capital with addon authors with which to force them to make compatibility fixes - at some point, some number of them get fed up and stop updating their code. I'm really not sure that this is a worthy place to

Re: ES6 lexical temporal dead zone has landed on central

2014-09-18 Thread Jorge Villalobos
Kris from the Add-ons Team is already looking into this and will message developers affected by this issue. Jorge On 9/18/14, 1:47 AM, Philipp Kewisch wrote: Is the AMO compatibility checker powerful enough to detect at least the first category of required changes? If so I don't think we

Re: Intent to ship: CSS Filters

2014-09-18 Thread Max Vujovic
On Sep 16, 2014, at 9:52 PM, Dirk Schulze dschu...@adobe.com wrote: On Sep 17, 2014, at 2:44 AM, L. David Baron dba...@dbaron.org wrote: On Tuesday 2014-09-16 16:31 -0700, Rik Cabanier wrote: On Tue, Sep 16, 2014 at 2:44 PM, L. David Baron dba...@dbaron.org wrote: On Tuesday

Reminder: Tree Closing Window, Sat Sep 20, 0900-1300 PT

2014-09-18 Thread Hal Wine
See below for details - to check status, please visit #moc in IRC or https://status.mozilla.org/en-US/calendar/ Main bug for whistlepig: 1065514 Short Summary: Mozilla IT will have a infrastructure maintenance window on Saturday, September 20th, from 0900-1300 PDT. During this window we will

Re: ES6 lexical temporal dead zone has landed on central

2014-09-18 Thread Jonas Sicking
On Thu, Sep 18, 2014 at 1:41 AM, Bobby Holley bobbyhol...@gmail.com wrote: It would probably be easy for them to fix, yes. But we have a roughly fixed amount of capital with addon authors with which to force them to make compatibility fixes - at some point, some number of them get fed up and

Re: ES6 lexical temporal dead zone has landed on central

2014-09-18 Thread Kent James
On 9/17/2014 7:51 PM, Bill McCloskey wrote: If this change proves to be really disruptive to add-on authors, I wonder if we could just make let behave like var for add-ons? The JS tokenizer could just substitute var for let when parsing code from an add-on compartment. (Bug 1030420 will put