Re: Intent to implement: -webkit-background-clip:text

2016-03-21 Thread Jet Villegas
I'd like to see this guarded by its own pref && layout.css.prefixes.webkit Thanks for working on this, CJ! --Jet On Tue, Mar 22, 2016 at 1:59 PM, Ku(顧思捷)CJ wrote: > Summary: > -webkit-background-clip:text has been available for years in webkit based > browsers and has seen widespread usage on

Intent to implement and ship: text-combine-upright: all

2016-03-21 Thread Xidorn Quan
Summary: According to some people from Japanese ebook companies, text-combine-upright (a.k.a horizontal-in-vertical, or tate-chu-yoko) is a must for Japanese vertical layout. Without the proper support of this feature, a book may not be considered complete, and thus cannot be sold online. This is a

Intent to implement: -webkit-background-clip:text

2016-03-21 Thread 顧思捷
Summary: -webkit-background-clip:text has been available for years in webkit based browsers and has seen widespread usage on the web. This css property is currently available in Chrome, Safari and Edge. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=759568 Link to standard: https://compat.spec

Re: Test automation addons and signing

2016-03-21 Thread Martijn
So the xpinstall.signatures.required=false pref in about:config trick doesn't work anymore for trunki? Regards, Martijn On Tue, Mar 1, 2016 at 5:48 AM, Philip Chee wrote: > On 28/02/2016 09:45, Bobby Holley wrote: > > >> We were promised that trunk and aurora builds would not enforce addon > >>

Re: b2g builds on trunk- perma failing for weeks?

2016-03-21 Thread Juan Gómez
Yep, I could finally fix this bustage and the patch it's just waiting to be landed. Once it happens, builds won't be fixed immediately because we still need to push a prebuilt image to one of our servers so once all the bits are in place, treeherder will show a beautiful green tree again... eventua

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread Petr Cerny
Henri Sivonen wrote: > Sure, once you are on similar level of stability to GCC, it is not such > a big problem. Note that GCC 5.3.0 (to my best knowledge) can be > compiled by GCC-3.4 (10 years difference). Once rustc is capable of > being compiled by a one or two years older version of itsel

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread Henri Sivonen
On Mar 21, 2016 7:21 PM, "Petr Cerny" wrote: > > Sure, once you are on similar level of stability to GCC, it is not such > a big problem. Note that GCC 5.3.0 (to my best knowledge) can be > compiled by GCC-3.4 (10 years difference). Once rustc is capable of > being compiled by a one or two years

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread Henri Sivonen
On Mon, Mar 21, 2016 at 6:49 PM, wrote: > I'm surprised to hear that *10.4* is still expected to work. The oldest > version I've heard Rust needed to support is 10.6. 10.6 on Intel is the oldest supported by Mozilla. Cameron maintains a port to 10.4 on PPC: http://www.floodgap.com/software/tenf

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread Petr Cerny
bander...@mozilla.com wrote: >> Actually, this would be pretty much what GCC does: it bootstraps >> itself in three phases, with just one `make` command. And although >> the scale is much longer, compiling for example GCC-5.3.0 with GCC > > This is also what rustc does - it bootstraps off of itsel

Re: MOZ_LOG_FILE and MOZ_LOG_MODULES are now the environment variables for logging

2016-03-21 Thread Nicholas Alexander
On Mon, Mar 21, 2016 at 9:13 AM, Honza Bambas wrote: > tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't > worry about backward compatibility tho, when MOZ_LOG_* is not set, we > fallback to NSPR_LOG_* values. > Hi Honza, Thanks for making the world a better place! I'm s

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread banderson
On Monday, March 21, 2016 at 9:43:24 AM UTC-7, Petr Cerny wrote: > Chris Peterson wrote: > > On 3/20/16 3:04 AM, Henri Sivonen wrote: > >> On Sat, Mar 19, 2016 at 2:27 PM, wrote: > >>> > On Thursday, 17 March 2016 12:23:32 UTC, Henri Sivonen wrote: > >> (rustc originally bootstrapped with O

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread banderson
On Sunday, March 20, 2016 at 3:05:25 AM UTC-7, Henri Sivonen wrote: > On Fri, Mar 18, 2016 at 6:45 PM, Mike Hommey wrote: > > On Fri, Mar 18, 2016 at 05:23:21PM +0200, Henri Sivonen wrote: > >> You say you don't see #5 happening. Do you see #4 happening? If not, > >> what do you see happening? > >

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread banderson
On Saturday, March 19, 2016 at 9:18:21 PM UTC-7, Cameron Kaiser wrote: > On 3/19/16 5:27 AM, cosinusoida...@gmail.com wrote: > > On Thursday, 17 March 2016 12:23:32 UTC, Henri Sivonen wrote: > >> On Thu, Mar 17, 2016 at 1:58 PM, Martin Stransky > >> wrote: > >>> Is it possible to build Rust from

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread Petr Cerny
Chris Peterson wrote: > On 3/20/16 3:04 AM, Henri Sivonen wrote: >> On Sat, Mar 19, 2016 at 2:27 PM, wrote: >>> > On Thursday, 17 March 2016 12:23:32 UTC, Henri Sivonen wrote: >> (rustc originally bootstrapped with OCaml, but >> building the whole history of Rust from the OCaml days to

MOZ_LOG_FILE and MOZ_LOG_MODULES are now the environment variables for logging

2016-03-21 Thread Honza Bambas
tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't worry about backward compatibility tho, when MOZ_LOG_* is not set, we fallback to NSPR_LOG_* values. The longer version: Since the new logging code sits in XPCOM and has no longer anything to do with NSPR and NSPR loggi

Re: b2g builds on trunk- perma failing for weeks?

2016-03-21 Thread Fabrice Desré
On 03/21/2016 08:31 AM, jmaher wrote: I have noticed that since March 4th, the b2g builds on m-c are perma failing. Doing some basic searching we have about 15 hours of machine time going to failed builds on every push (which is ~1350 builds or 20,250 machine hours). These show up in mozrevie

RE: Intent to switch to Visual Studio 2015

2016-03-21 Thread Yuhong Bao
> On 2016-03-18 6:43 PM, Yuhong Bao wrote: >> >>> On 2016-03-17 8:35 PM, Yuhong Bao wrote: > On Thu, Mar 17, 2016 at 3:30 PM, > mailto:yuhongbao_...@hotmail.com>> wrote: > What about the depreciation of XP SP2? > > Results from bug 1124017 say XP SP2 still works on binaries buil

RE: Intent to switch to Visual Studio 2015

2016-03-21 Thread Yuhong Bao
> On 2016-03-17 8:35 PM, Yuhong Bao wrote: >>> On Thu, Mar 17, 2016 at 3:30 PM, >>> mailto:yuhongbao_...@hotmail.com>> wrote: >>> What about the depreciation of XP SP2? >>> >>> Results from bug 1124017 say XP SP2 still works on binaries built with >>> VS2015u1. This may not always hold true. So we

b2g builds on trunk- perma failing for weeks?

2016-03-21 Thread jmaher
I have noticed that since March 4th, the b2g builds on m-c are perma failing. Doing some basic searching we have about 15 hours of machine time going to failed builds on every push (which is ~1350 builds or 20,250 machine hours). These show up in mozreview as failed jobs when you autoland a pus

[Firefox Desktop] Issues found: March 14th to March 18th

2016-03-21 Thread Andrei Vaida
Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA team last week, *March 14 - March 18* (week 11). Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://public.etherpad-mozilla.org/p/D

Re: Linux distro readiness for Rust in Gecko

2016-03-21 Thread Henri Sivonen
On Sun, Mar 20, 2016 at 9:53 PM, Petr Cerny wrote: > I can't speak for Debian, but on SLE the solution we went for last time was > packaging new-enough GCC for older supported code streams, very much like > other packages (e.g. GTK) we had already needed way before. This seems like a reasonable s

Build System Project - Update from the last 2 weeks

2016-03-21 Thread David Burns
Below is a highlight of all work the build peers have done in the last 2 weeks as part of their work to modernise the build infrastructure. Since the last report[1] we have seen thousands of lines of configure and m4 code removed from mozilla-central. We have removed over 30 Makefiles from mozilla