On Tue, May 10, 2016 at 10:58:25PM -0400, Lawrence Mandel wrote:
> On Fri, May 6, 2016 at 6:43 AM, Xidorn Quan wrote:
>
> > On Fri, May 6, 2016 at 8:24 PM, Mike Hommey wrote:
> >
> > > On Fri, May 06, 2016 at 06:01:12PM +1000, Xidorn Quan wrote:
> > > >
> > > > It's Firefox 48, three versions af
On Fri, May 6, 2016 at 6:43 AM, Xidorn Quan wrote:
> On Fri, May 6, 2016 at 8:24 PM, Mike Hommey wrote:
>
> > On Fri, May 06, 2016 at 06:01:12PM +1000, Xidorn Quan wrote:
> > >
> > > It's Firefox 48, three versions after ESR 45, which is roughly halfway
> > > before the next ESR.
> >
> > 48 is t
On Tue, May 10, 2016 at 6:55 PM, Lawrence Mandel
wrote:
> On Fri, May 6, 2016 at 12:39 PM, Benjamin Smedberg
> wrote:
>
> > I agree that we should drop support for non-SSE2. It mattered 7 years ago
> > (see https://bugzilla.mozilla.org/show_bug.cgi?id=500277) but it really
> > doesn't matter now
On Wed, May 11, 2016 at 11:51 AM, Lawrence Mandel
wrote:
>
> On Tue, May 10, 2016 at 7:29 PM, Xidorn Quan
> wrote:
>
>> On Wed, May 11, 2016 at 6:45 AM, Gregory Szorc wrote:
>>
>> > On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote:
>> >
>> > > There is a compiler bug in VS2015 that results i
On Fri, May 6, 2016 at 12:39 PM, Benjamin Smedberg
wrote:
> I agree that we should drop support for non-SSE2. It mattered 7 years ago
> (see https://bugzilla.mozilla.org/show_bug.cgi?id=500277) but it really
> doesn't matter now.
>
> We do need to avoid updating these users to a build that will c
On Tue, May 10, 2016 at 7:29 PM, Xidorn Quan wrote:
> On Wed, May 11, 2016 at 6:45 AM, Gregory Szorc wrote:
>
> > On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote:
> >
> > > There is a compiler bug in VS2015 that results in SSE instructions
> being
> > > emitted when they shouldn't be. Since
On Tue, May 10, 2016 at 7:05 PM, Ehsan Akhgari
wrote:
> On 2016-05-10 4:45 PM, Gregory Szorc wrote:
> > On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote:
> >
> >> There is a compiler bug in VS2015 that results in SSE instructions being
> >> emitted when they shouldn't be. Since Firefox still
On Tue, May 10, 2016 at 1:31 PM, Mike Taylor wrote:
> On 5/10/16 3:05 PM, Jack Moffitt wrote:
>
>> We have the Chrome popularity data, and we have the Edge team's data
>> which covers the CSS spectrum quite well. I think it would be far more
>> useful to start covering the DOM API spectrum.
>>
>>
On Wed, May 11, 2016 at 6:45 AM, Gregory Szorc wrote:
> On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote:
>
> > There is a compiler bug in VS2015 that results in SSE instructions being
> > emitted when they shouldn't be. Since Firefox still needs to remain
> > compatible with ancient hardware
On 2016-05-10 4:45 PM, Gregory Szorc wrote:
> On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote:
>
>> There is a compiler bug in VS2015 that results in SSE instructions being
>> emitted when they shouldn't be. Since Firefox still needs to remain
>> compatible with ancient hardware that doesn't
Hello All,
In order to support features in the WebVR 1.0 API
(https://mozvr.com/webvr-spec/) and to improve performance for WebVR, I would
like to implement an optimized path for submitting Canvas and OffscreenCanvas
frames to VR headsets. The WebVR 1.0 API introduces "VR Layers", explicit
fr
On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote:
> There is a compiler bug in VS2015 that results in SSE instructions being
> emitted when they shouldn't be. Since Firefox still needs to remain
> compatible with ancient hardware that doesn't support SSE, this is causing
> crashes on Firefox b
On 5/10/16 3:05 PM, Jack Moffitt wrote:
We have the Chrome popularity data, and we have the Edge team's data
which covers the CSS spectrum quite well. I think it would be far more
useful to start covering the DOM API spectrum.
For example, it's pretty clear from existing data sources which CSS
p
On 05/10/2016 01:05 PM, Jack Moffitt wrote:
We have the Chrome popularity data, and we have the Edge team's data
which covers the CSS spectrum quite well. I think it would be far more
useful to start covering the DOM API spectrum.
For example, it's pretty clear from existing data sources which C
We have the Chrome popularity data, and we have the Edge team's data
which covers the CSS spectrum quite well. I think it would be far more
useful to start covering the DOM API spectrum.
For example, it's pretty clear from existing data sources which CSS
properties Servo should focus on. But we ha
On 5/10/16 2:11 PM, Mike Taylor wrote:
Having recently discovered UseCounters.conf[1], I'd like to add use
counters for all CSS properties, starting with prefixed props. And
likewise for Moz-prefixed DOM props and methods.
Link to bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1271752
--
M
Having recently discovered UseCounters.conf[1], I'd like to add use
counters for all CSS properties, starting with prefixed props. And
likewise for Moz-prefixed DOM props and methods.
Ultimately, I'd like us to have a Firefox equivalent to
https://www.chromestatus.com/metrics/css/popularity to
err [1] is https://wiki.mozilla.org/Telemetry/Experiments and [2] is
https://wiki.mozilla.org/QA/Telemetry/Developing_a_Telemetry_Experiment
:)
On Tue, May 10, 2016 at 10:53 AM, Kartikaya Gupta wrote:
> Just to close the loop on this, I went ahead and updated the wiki
> pages at [1] and [2] to re
Just to close the loop on this, I went ahead and updated the wiki
pages at [1] and [2] to reflect that some parts of the process are
more optional than they originally seemed. I also tried to generally
make the documentation simpler to follow and less
redundant/contradictory. Finally, I filed bug 1
19 matches
Mail list logo