Re: Using a pre-processing flag to auto-disable features in later Beta versions

2013-04-19 Thread Steve Fink
On Fri 19 Apr 2013 04:27:22 PM PDT, Asa Dotzler wrote: > On 4/19/2013 4:04 PM, Robert O'Callahan wrote: >> On Sat, Apr 20, 2013 at 10:34 AM, Asa Dotzler wrote: >> >>> That would be great -- if we had a significantly larger Aurora >>> population.. >>> Right now, the only way to get anything close

Re: Using a pre-processing flag to auto-disable features in later Beta versions

2013-04-19 Thread Robert O'Callahan
On Sat, Apr 20, 2013 at 11:27 AM, Asa Dotzler wrote: > I don't think it's that black and white. PDF.js and our new Cookie policy > are both user facing features and web compat concerns that need a crap ton > of compat testing. Hmm, PDF.js yes, maybe click to play too. But for cookie policy, Sh

Re: Using a pre-processing flag to auto-disable features in later Beta versions

2013-04-19 Thread Asa Dotzler
On 4/19/2013 4:04 PM, Robert O'Callahan wrote: On Sat, Apr 20, 2013 at 10:34 AM, Asa Dotzler wrote: That would be great -- if we had a significantly larger Aurora population.. Right now, the only way to get anything close to decent "did we break the web" testing is on our Beta channel. I

Re: Using a pre-processing flag to auto-disable features in later Beta versions

2013-04-19 Thread Robert O'Callahan
On Sat, Apr 20, 2013 at 10:34 AM, Asa Dotzler wrote: > That would be great -- if we had a significantly larger Aurora population. > Right now, the only way to get anything close to decent "did we break the > web" testing is on our Beta channel. > I think Daniel was concerned about user-visible

Re: Using a pre-processing flag to auto-disable features in later Beta versions

2013-04-19 Thread Asa Dotzler
On 4/19/2013 3:17 PM, Daniel Holbert wrote: Would this mean that Beta-channel users would see some features appear on release-day, and then disappear a couple weeks later, and then those same features (plus maybe some new ones) would suddenly reappear on the next release day, and then potentially

Re: Using a pre-processing flag to auto-disable features in later Beta versions

2013-04-19 Thread Daniel Holbert
Would this mean that Beta-channel users would see some features appear on release-day, and then disappear a couple weeks later, and then those same features (plus maybe some new ones) would suddenly reappear on the next release day, and then potentially disappear again? (etc) This seems like it co

Re: Rendering meeting, Monday at 2:30 PM US/Pacific

2013-04-19 Thread Benoit Jacob
Reminder: rendering meeting this coming Monday! See below. 2013/4/13 Benoit Jacob > Hello, > > The next Rendering meeting will take place *not* this Monday, but on > Monday April 22 at 2:30 PM US/Pacific time. That could be Tuesday in your > timezone. > > The Rendering meeting is about all thin

Re: Revamping touch input on Windows

2013-04-19 Thread smaug
On 04/18/2013 03:50 PM, Jim Mathies wrote: 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 rat

Re: Using a pre-processing flag to auto-disable features in later Beta versions

2013-04-19 Thread Alex Keybl
Johnathan and I also spoke about this last week, and we were going to sync up with Gavin to work out details and find an owner for channel-specific preference enables/disables. We'd only discussed having Nightly-only, up to Aurora, and up to Beta. Up to early beta is a good addition. Let me set