I'm with Jeff on this one. I'm very much against special casing add-on code --
which will invariably develop into another compatibility to break when we
finally do decide to break it.
- Original Message -
From: "Jeff Walden"
To: dev-platform@lists.mozilla.org
Sent: Friday, September 19,
On 9/19/14, 8:23 PM, L. David Baron wrote:
W3C recently published the following proposed recommendation (the
stage before W3C's final stage, Recommendation):
The biggest issue I have with this is exiting CR without anything
resembling a comprehensive enough test suite to ensure anything like
On 09/18/2014 04:18 PM, Kent James wrote:
> Substituting var for let does not result in code that behaves identically to
> previous code, so I can't see why that would be proposed.
The proposal would be to perform the substitution only for let at "body level"
of a function. (And for global let
W3C recently published the following proposed recommendation (the
stage before W3C's final stage, Recommendation):
http://www.w3.org/TR/html5/
HTML5
There's a call for review to W3C member companies (of which Mozilla
is one) open until October 14.
This specification is largely based on a sna
Regarding dropping support, Silverlight on Mac does not support 64 bit and
we run it using 32 bit. So at the very least we will need html5 for sites
like Netflix before we can drop 32 bit support on OS X.
Robert
> -Original Message-
> From: dev-platform [mailto:dev-platform-
> bounces+rst
As I have read [1] that Google will drop support for 32bit mode of
Chrome with the upcoming 39 release in November. I wonder what our
support plans for 32bit mode on OS X look like. Is it something we want
to keep, to allow e.g. users of Chrome, who cannot run a 64bit version
of Chrome, to switch o
6 matches
Mail list logo
