On Tuesday, June 20, 2017 at 1:28:50 PM UTC-4, Ehsan Akhgari wrote:
> > My understanding is that the slowdown cannot be reproduced on local
> > developer machines, but can be reproduced on loaner machines from
> > infra.
> Huh. That's interesting and even more puzzling...
> > I don't think anybody
On 06/20/2017 04:42 PM, Gregory Szorc wrote:
On Tue, Jun 20, 2017 at 10:28 AM, Ehsan Akhgari
mailto:ehsan.akhg...@gmail.com>> wrote:
On 06/20/2017 12:28 PM, Nathan Froyd wrote:
On Tue, Jun 20, 2017 at 12:19 PM, Ehsan Akhgari
mailto:ehsan.akhg...@gmail.com>> wrote:
Yeah - stylo for the frontend would be nice, but it's not part of our MVP.
It wouldn't be hard, just presumably implementing a few more scattered
internal things and fixing more bugs exposed by the heavier usage of XBL.
But we could ship in 57 without it, and so it seems foolish to widen our
scope
On 06/21/2017 06:19 AM, Chris Cooper wrote:
On Tuesday, June 20, 2017 at 1:28:50 PM UTC-4, Ehsan Akhgari wrote:
My understanding is that the slowdown cannot be reproduced on local
developer machines, but can be reproduced on loaner machines from
infra.
Huh. That's interesting and even more puz
On 06/20/2017 01:20 AM, Cameron McCormack wrote:
On Tue, Jun 20, 2017, at 01:08 PM, Jared Wein wrote:
We use a scoped stylesheet for styling the popup for [1]. We
chose this route to limit performance impact as well as limit our
temporary stylesheet from affecting other parts of the browser UI.
On 6/21/17 10:44 AM, Ehsan Akhgari wrote:
It seems like that we have an answer now in the bug!
https://bugzilla.mozilla.org/show_bug.cgi?id=1338651#c129
Just for clarity, so people don't have to read the whole bug, changing
the _path_ the build is at when it's compiled/linked results in the hu
On Wed, Jun 21, 2017, at 10:56 PM, Ehsan Akhgari wrote:
> Why only in the medium term? Restyling is very costly for browser.xul
> right now, and it would be very nice if we can use Stylo to gain some
> advantages there, especially since costly restyles in the parent process
> do mean UI jank fo
On 6/21/17 8:06 AM, Boris Zbarsky wrote:
On 6/21/17 10:44 AM, Ehsan Akhgari wrote:
It seems like that we have an answer now in the bug!
https://bugzilla.mozilla.org/show_bug.cgi?id=1338651#c129
Just for clarity, so people don't have to read the whole bug, changing
the _path_ the build is at w
On 06/21/2017 09:56 AM, Chris Peterson wrote:
On 6/21/17 8:06 AM, Boris Zbarsky wrote:
On 6/21/17 10:44 AM, Ehsan Akhgari wrote:
It seems like that we have an answer now in the bug!
https://bugzilla.mozilla.org/show_bug.cgi?id=1338651#c129
Just for clarity, so people don't have to read the wh
On Wed, Jun 21, 2017 at 8:13 AM, Cameron McCormack wrote:
> On Wed, Jun 21, 2017, at 10:56 PM, Ehsan Akhgari wrote:
>> Why only in the medium term? Restyling is very costly for browser.xul
>> right now, and it would be very nice if we can use Stylo to gain some
>> advantages there, especially sin
(I apologize for the late notice on this, I forgot to include dev-platform
in the original earlier email)
At 11:00PT today, we will be landing patches to run mac opt builds on trunk
as cross compiled builds on Linux machines on taskcluster. As this change
is uplifted to m-c, nightly builds for m
I have filed https://bugzilla.mozilla.org/show_bug.cgi?id=1375224 and
attached a patch to remove our dependency on
On 6/21/17 2:38 PM, Kim Moir wrote:
At 11:00PT today, we will be landing patches to run mac opt builds on trunk
as cross compiled builds on Linux machines on taskcluster.
I just wanted to thank everyone who has worked on this change. I know
there were a bunch of nasty obstacles to making this
+1 to that. So great to see so many parts of the org coming together to
make something like this happen!
On Wed, Jun 21, 2017 at 2:00 PM, Boris Zbarsky wrote:
> On 6/21/17 2:38 PM, Kim Moir wrote:
>
>> At 11:00PT today, we will be landing patches to run mac opt builds on
>> trunk
>> as cross com
We're starting to enable the *building* (not enabling) of Stylo in various
platforms in automation. This means that Nightly will start shipping Stylo
bits soon - possibly the next Nightly if things stick.
The roll-out is being done as platforms are ready. Linux 64-bit and Windows
64-bit are the pr
+cc: dev-servo, dev-tech-layout
Also, \o/ !!!
On Wed, Jun 21, 2017 at 3:24 PM, Gregory Szorc wrote:
> We're starting to enable the *building* (not enabling) of Stylo in various
> platforms in automation. This means that Nightly will start shipping Stylo
> bits soon - possibly the next Nightly if
If you're building Firefox from source, please check that your rust
toolchain is up-to-date. You can either:
rustup update
or
./mach bootstrap
We've just queued a patch to bump the minimum required rust version from
1.15.1 to 1.17.0, the version released 8 weeks ago. This is necessary for
m
Status update:
We have successful cross compiled macosx opt builds running on trunk. We
also have run a successful nightly cross compiled nightly on m-c. We are
going to leave the rule in place that blocks updates for macosx nightlies
so we can test and update from tonight's nightly to tomorrow'
>At 11:00PT today, we will be landing patches to run mac opt builds on trunk
>as cross compiled builds on Linux machines on taskcluster. As this change
>is uplifted to m-c, nightly builds for mac will also switch to run on
>taskcluster on Linux. We will be testing to ensure that updates work as
>
On Wed, Jun 21, 2017 at 9:47 PM, Randell Jesup
wrote:
> Does this have affect on our still using the 10.7 Mac SDK?
We are still building against the macOS 10.7 SDK, but we can update to 10.9
once we've confirmed transition away from the 10.7 builders.
-r
_
20 matches
Mail list logo
