>> The metro/WinRT widget backend can take advantage of native gesture
>> recognition, so maybe in the future we would want to implement the
>> ability to opt-out of front-end gesture recognition. I don't think we
>> should do this in the immediate term, but as backends get better and
>> better nat
hi;
We will have a treeclosing maintenance window Sunday, April 21 from
10:00-14:00PT (17:00-21:00UTC). This is for changes and upgrades to
firewalls in the scl3 colo. More details in tracking bug
https://bugzil.la/862956.
All trees will be closed during this period. Jobs in progress at start
of
On 4/18/2013 12:10 PM, Matt Brubeck wrote:
Since we run PGO builds only a few times a day, the ranges can be large.
For those that include m-c merges, you could narrow them down using
the m-c data. WebIDL seems to be a common theme.
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=863492
Lukas Blakk schrieb:
* Releng automation to switch/edit mozconfigs for earlier betas to check for
this flag
I think it would be good if we wouldn't have to rely on releng there, as
this again introduces the factor of someone possibly forgetting to do
this. Ideally this should be fully automa
On Apr 18, 2013, at 1:18 PM, Gregory Szorc wrote:
>
> I think this is a good idea. I've wanted it for a while as well. I've even
> already filed a build config bug to support it:
> https://bugzilla.mozilla.org/show_bug.cgi?id=853071.
>
> What we don't have are specific and common use cases th
On 04/18/13 04:03 PM, Lukas Blakk wrote:
> Hello,
>
> I'm following up on an action from our Firefox 20 Post-Mortem where it was
> discussed that it would be helpful to have a way to pref on a set of features
> that want to be in early Beta builds to garner feedback and audience reach
> but sho
On 4/18/13 1:03 PM, Lukas Blakk wrote:
Hello,
I'm following up on an action from our Firefox 20 Post-Mortem where it was
discussed that it would be helpful to have a way to pref on a set of features
that want to be in early Beta builds to garner feedback and audience reach but
should not ship
Hello,
I'm following up on an action from our Firefox 20 Post-Mortem where it was
discussed that it would be helpful to have a way to pref on a set of features
that want to be in early Beta builds to garner feedback and audience reach but
should not ship since they are not ready for public cons
On 4/17/2013 3:07 PM, Matt Brubeck wrote:
analyze_talos.py does identify several real regressions in that dataset
-- but it suppresses emails for them because each one is an increase of
less than 2% (see bug 822249). Here are regressions identified by the
latest version of analyze.py:
In case
"Tim Abraldes" wrote in message
news:...
> > 1) abandon generating nsIDOMSimpleGestureEvents on Windows for both
> backends
> > when processing touch input from touch input displays.*
> >
> > This would mean that if the desktop front end wants to do something with
> > pinch or zoom, it would have
> 1) abandon generating nsIDOMSimpleGestureEvents on Windows for both
backends
> when processing touch input from touch input displays.*
>
> This would mean that if the desktop front end wants to do something with
> pinch or zoom, it would have to process W3C touch events instead. Note
that
> we co
We have quite a few issues with touch enabled sites on Windows. [1] Our
support for touch stretches back to when we first implemented MozTouch
events which over time has morphed into a weird combination of W3C touch /
simple gestures support. It is rather messy to fix, but I'd like to get this
On 17/04/2013 20:51, Ms2ger wrote:
On 04/17/2013 09:36 PM, Gregory Szorc wrote:
It /could/, sure. However, I consider auto clobbering a core build
system feature (sheriffs were very vocal about wanting it). As such, it
needs to be part of client.mk. (Please correct me if I am wrong.)
This shou
13 matches
Mail list logo
