I have a slight twist in thinking to offer on the topic of persistent
permissions.. part of this falls to the level of spitballing so forgive the
imprecision:
Restricting persistent permissions is essentially about cache poisoning
attacks. The assumptions seem to be that
a] https is not
On Wednesday, 11 March 2015 10:54:59 UTC, bo...@mozilla.com wrote:
On Tuesday, March 10, 2015 at 5:06:31 PM UTC, Ehsan Akhgari wrote:
Here's a push in case the bugs don't exist in certain builds:
https://treeherder.mozilla.org/#/jobs?repo=tryrevision=044e896fc6fa
I was looking at
On Wednesday, March 11, 2015 at 9:10:43 PM UTC+1, bobow...@gmail.com wrote:
On Wednesday, 11 March 2015 10:54:59 UTC, bo...@mozilla.com wrote:
On Tuesday, March 10, 2015 at 5:06:31 PM UTC, Ehsan Akhgari wrote:
Here's a push in case the bugs don't exist in certain builds:
On 2015-03-11 2:13 PM, Gregory Szorc wrote:
On Wed, Mar 11, 2015 at 10:21 AM, Ehsan Akhgari ehsan.akhg...@gmail.com
mailto:ehsan.akhg...@gmail.com wrote:
On 2015-03-11 7:35 AM, Brian Smith wrote:
Mike Hommey m...@glandium.org mailto:m...@glandium.org wrote:
Brian Smith
On Wed, Mar 11, 2015 at 10:21 AM, Ehsan Akhgari ehsan.akhg...@gmail.com
wrote:
On 2015-03-11 7:35 AM, Brian Smith wrote:
Mike Hommey m...@glandium.org wrote:
Brian Smith wrote:
It is very inconvenient to have a minimum supported compiler version
that we cannot even do test builds with
On 03/11/2015 07:13 PM, Gregory Szorc wrote:
This build environment would be defined inside
mozilla-central in such a way that it is reproducible over time. e.g.
update your source repo to a commit from March 2015 and you automatically
get the build environment that was used in March 2015.
On 09.03.2015 02:44, Ryan VanderMeulen wrote:
For the past many months, I have been working on some major updates to the
Mozillabuild package in order to make it more developer-friendly and
easily-maintainable in the future. I am proud to say that at this time, it
is ready for more widespread
On Wednesday, March 11, 2015 at 5:14:39 PM UTC, Ehsan Akhgari wrote:
On 2015-03-11 8:34 AM, bo...@mozilla.com wrote:
Given that we (and probably Chromium) would be unlikely to drop MSVC 2013
before our next ESR anyway
That is not true. The compiler that we use to build ESR has nothing to
More context would be helpful. I personally run it out of
c:\mozilla-build-test without issues. Are you using spaces in the path by
chance?
On Wed, Mar 11, 2015 at 3:21 PM, Chris Pearce cpea...@mozilla.com wrote:
If I install this into a directory other than c:\mozilla-build I get an
error
On 3/11/2015 1:13 PM, Gregory Szorc wrote:
So I guess we trend towards supporting 2 build modes: Mozilla's official
build environment via containers/chroots (preferred) or host native (for
the people who insist on using it). Only host native exists today and it
is a PITA.
Using docker
Ah yes, I installed it to a patch with a space in it. Thanks!
cpearce.
On Thu, Mar 12, 2015 at 8:28 AM, Ryan VanderMeulen
rvandermeu...@mozilla.com wrote:
More context would be helpful. I personally run it out of
c:\mozilla-build-test without issues. Are you using spaces in the path by
If I install this into a directory other than c:\mozilla-build I get an
error dialog popup saying can't find c:\mozilla-build or somesuch. Maybe
there's a path hardcoded somewhere? It's a bit of a footgun since the
installer defaults to a non c:\mozilla-build install dir.
Thanks very much for
Hi all,
Project Silk (http://www.masonchang.com/blog/2015/1/22/project-silk), which
aligns rendering to vsync, will be landing over the next couple of weeks (bug
1071275). You should expect smoother animations and scrolling while browsing
the web. It'll land in 4 parts, with the vsync
I've posted a followup of sorts to public-houdini:
https://lists.w3.org/Archives/Public/public-houdini/2015Mar/0020.html
There have been no replies, so I suspect I've said something terribly
incomprehensible and/or wrong :-).
Rob
--
oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso
On Wed, Mar 11, 2015 at 2:30 PM, Ehsan Akhgari ehsan.akhg...@gmail.com
wrote:
On 2015-03-11 2:13 PM, Gregory Szorc wrote:
On Wed, Mar 11, 2015 at 10:21 AM, Ehsan Akhgari ehsan.akhg...@gmail.com
mailto:ehsan.akhg...@gmail.com wrote:
On 2015-03-11 7:35 AM, Brian Smith wrote:
On Tue, Mar 10, 2015 at 07:23:36PM -0700, Brian Smith wrote:
bo...@mozilla.com wrote:
In summary: Officially make gcc-4.7 our minimum supported version. Fx38 and
39 don't compile with 4.6 and none of the GNU/Linux package maintainers I
have contacted have any major concerns over dropping
Mike Hommey m...@glandium.org wrote:
Brian Smith wrote:
It is very inconvenient to have a minimum supported compiler version
that we cannot even do test builds with using tryserver.
Why this sudden requirement when our *current* minimum supported
version is 4.6 and 4.6 is nowhere close to
On Tuesday, March 10, 2015 at 5:06:31 PM UTC, Ehsan Akhgari wrote:
Here's a push in case the bugs don't exist in certain builds:
https://treeherder.mozilla.org/#/jobs?repo=tryrevision=044e896fc6fa
I was looking at the log for a B2G Device Image build (I think it
was the one for Nexus
Hi all,
I am giving the heads up that Off-main-thread compositing (OMTC) will soon
be enabled on Linux and that there are some expected talos regressions.
In particular, a fairly big one in tp5o_scroll (see the compare-talos link
below).
bo...@mozilla.com wrote:
Also, from what I can tell of the C++ features that gcc-4.8 enables (from
[1]), none of them are available until MSVC 2015.
It seems likely that we'll be supporting MSVC 2013 until the next ESR, so I
don't see that moving to 4.8 gives us any immediate benefits.
[1]
On Wednesday, March 11, 2015 at 11:53:11 AM UTC, Brian Smith wrote:
bo...@mozilla.com wrote:
Also, from what I can tell of the C++ features that gcc-4.8 enables (from
[1]), none of them are available until MSVC 2015.
It seems likely that we'll be supporting MSVC 2013 until the next ESR, so
On Wednesday, March 11, 2015 at 8:40:46 AM UTC, Mike Hommey wrote:
On Tue, Mar 10, 2015 at 07:23:36PM -0700, Brian Smith wrote:
bo...@mozilla.com wrote:
In summary: Officially make gcc-4.7 our minimum supported version. Fx38
and 39 don't compile with 4.6 and none of the GNU/Linux package
Ryan VanderMeulen rya...@gmail.com wrote:
(2) The trychooser tool should be extended to make it possible to
build with GCC 4.7 on any platforms where it is supported, and
bootstrap.py be updated to install GCC 4.7 alongside the
currently-installed compiler.
All Android and B2G JB/KK emulator
On 3/11/15 2:56 PM, Juan Gómez wrote:
AFAIK, in B2G we are tied to the same host compiler version that our Android
base platform needs. This is gcc-4.6 for ICS and JB devices (not really sure if
KK/LL works with newer ones, but I'll bet they do).
Of course, we could fix any incompatibilty and
On 2015-03-11 8:36 PM, Gregory Szorc wrote:
On Wed, Mar 11, 2015 at 2:30 PM, Ehsan Akhgari ehsan.akhg...@gmail.com
mailto:ehsan.akhg...@gmail.com wrote:
On 2015-03-11 2:13 PM, Gregory Szorc wrote:
On Wed, Mar 11, 2015 at 10:21 AM, Ehsan Akhgari
ehsan.akhg...@gmail.com
On 2015-03-11 6:05 PM, Chris Peterson wrote:
On 3/11/15 2:56 PM, Juan Gómez wrote:
AFAIK, in B2G we are tied to the same host compiler version that our
Android base platform needs. This is gcc-4.6 for ICS and JB devices
(not really sure if KK/LL works with newer ones, but I'll bet they do).
Of
26 matches
Mail list logo
