Re: Tier 3 win64 ASan builds on try

Glorious. Thanks to everyone who made this happen. -Jeff On Thu, Apr 6, 2017 at 10:11 PM, Ting-Yu Chou wrote: > Just a heads up that now we have win64 ASan builds on try. The try format: > > try: -b o -p win64-asan -u none -t none > > Bug 1347793 is tracking the failed

Tier 3 win64 ASan builds on try

Just a heads up that now we have win64 ASan builds on try. The try format: try: -b o -p win64-asan -u none -t none Bug 1347793 is tracking the failed tests on taskcluster, though by now the tests for normal windows builds are not all green yet and I haven't seen any real ASan issue. I am not

Re: Changes to Firefox repositories on hg.mozilla.org

On 4/6/2017 7:13 PM, Gregory Szorc wrote: https://mozilla-version-control-tools.readthedocs.io/ en/latest/hgmozilla/installing.html Just to call it out explicitly since I've seen the question come up a number of times recently - Windows Mozillabuild users do *not* need to wait for a

mozIntl.DateTimeFormat

Hi all, We completed the transition of the Intl handling from using OS locale, to use browser UI locale. We have a new API called mozIntl.DateTimeFormat which should be the primary way we format date and time in our chrome. You can think of it as a regular ECMA402 DateTimeFormat on steroids.

Changes to Firefox repositories on hg.mozilla.org

This message applies to anyone who clones a Firefox repository from hg.mozilla.org. *Failure to read this message may result in degraded Mercurial performance.* If you use git-cinnabar or use the mozilla-unified repository exclusively, you are likely shielded from degraded performance and can stop

Moving the 53 Merge and Release dates to accomodate Easter holiday

Hi release-drivers and others, Because Monday April 17th is part of the Easter holiday in many countries, we decided to move the Firefox 53 merge and release dates by one day. Merge day will now be Tuesday, April 18, and we plan to release Firefox 53 on Wednesday, April 19. The dates are

Re: Intent to change editor newline behavior

On Thu, Apr 6, 2017 at 3:34 PM, Ehsan Akhgari wrote: > Thanks for the follow-ups and for filing bug 1354060. But now that we > know that this affected Gmail, I'll note that the risk around this is > still there, and while keeping this on the pre-release channels for a >

Re: Intent to change editor newline behavior

On 2017-04-06 7:51 AM, Aryeh Gregor wrote: > On Wed, Apr 5, 2017 at 11:22 PM, Daniel Veditz wrote: >> One line or a thousand isn't the point; building, release and update >> testing, and shipping 90 locales times 6 platforms is a huge amount work. If >> we have a pref and

Re: Enabling Pointer Events in Firefox (desktop) Nightly on Mac and Linux

On Thu, Apr 6, 2017 at 5:26 AM, Ehsan Akhgari wrote: > On Thu, Apr 6, 2017 at 12:57 AM, L. David Baron wrote: > > > On Thursday 2017-04-06 00:33 -0400, Ehsan Akhgari wrote: > > > In general, I should also say that designing features with > > >

Re: Enabling Pointer Events in Firefox (desktop) Nightly on Mac and Linux

On Thu, Apr 6, 2017 at 12:57 AM, L. David Baron wrote: > On Thursday 2017-04-06 00:33 -0400, Ehsan Akhgari wrote: > > In general, I should also say that designing features with > > fingerprinting in mind is *extremely* difficult and takes a lot of > > effort on the part of all

Re: Intent to change editor newline behavior

On Wed, Apr 5, 2017 at 11:22 PM, Daniel Veditz wrote: > One line or a thousand isn't the point; building, release and update > testing, and shipping 90 locales times 6 platforms is a huge amount work. If > we have a pref and break something we can back it out easily and

Re: Enabling Pointer Events in Firefox (desktop) Nightly on Mac and Linux

On Thursday, April 6, 2017 at 2:57:52 PM UTC+10, David Baron wrote: > On Thursday 2017-04-06 00:33 -0400, Ehsan Akhgari wrote: > > In general, I should also say that designing features with > > fingerprinting in mind is *extremely* difficult and takes a lot of > > effort on the part of all browser