On Thu, Mar 1, 2018, at 11:23 AM, Nicholas Alexander wrote:
> The requirement will likely be Node v8.9.4, the current LTS release.
MozillaBuild currently provides Node v8.9.0. If you are going to require a
version higher than that, probably it'd be better to coordinate with the A-team
to release
Hello dev-platform,
For the reasons outlined at
https://docs.google.com/document/d/1tOA2aeyjT93OoMv5tUMhAPOkf4rF_IJIHCAoJlwmDHI/edit?usp=sharing,
we would like to make Node a requirement to build Firefox sometime in the
Firefox 61 development cycle. (Firefox 60 will be an ESR release, so this
prov
As of bug 1433175, the mozilla/use-cc-etc eslint rule is enabled by
default. This means that any use of Components.classes,
Components.interfaces, Components.utils or Components.results will
cause linting errors. Please use the Cc, Ci, Cu, Cr shorthands instead
(they are defined in all chrome scope
I just want to give a huge thank you to everyone who worked on this. Its
such a monumental task to change such a core feature, especially with new
tests that might depend on the old behavior being added all the time.
Thank you!
Ben
On Wed, Feb 28, 2018 at 6:58 AM, Hiroyuki Ikezoe
wrote:
> Sum
Summary: We are about to land bug 1193394 which will change microtask
behavior that our microtask behavior complied with the HTML spec.
We had fixed all test failures but still it's possible that new failures
will
appear before the change gets merged into mozilla-central. If we found any
faile
On Wed, Feb 28, 2018 at 12:28 AM, Manish Goregaokar
wrote:
> You can already achieve this behavior with `rowspan=`,
In terms of letting HTML validation produce useful results, telling
authors to use a bogus large number is worse than having a special
value (zero). If you use 0 and the table makes
6 matches
Mail list logo
