Re: What are your use cases for the Touch Bar on the new MacBook Pro?

+1 on doing WebExt APIs in parallel - this can be done outside of mozilla-central on non-release channels using WebExtension Experiments (https://webextensions-experiments.readthedocs.io) Once the implementation in mozilla-central is settled down, the experimental API can be merged. On Tue, Jan

Re: What are your use cases for the Touch Bar on the new MacBook Pro?

I can see the advantage of addons exploring and iterating on this, but making the first version of this API addon-accessible might unnecessarily delay it. If there is enough interest in this, we might want to start this effort in parallel and release it in a subsequent version. On 1/3/17 4:31 PM,

Re: Intent to Implement: adding vector effects non-scaling-size, non-rotation and fixed-position to SVG

Hi Jeff > I'm concerned about the complexity this will add to the SVG implementation > as we're looking to transition to WebRender. if WebRender supports currently implemented "non-scaling-stroke", new modifications must be nothing more than recalculating CTM for those new effects. > Can the

Intent to vendor Servo in mozilla-central

Over in bug 1322769, we're planning to vendor the contents of the Servo Git repository into mozilla-central as part of Quantum efforts. The initial vendoring of the Servo repository is the first milestone of a larger project that aims to "unify" workflows and automation across the two projects,

Re: What are your use cases for the Touch Bar on the new MacBook Pro?

Will this API be accessible to addons? Seems like this would be a good place for people to explore and iterate. On 1/3/2017 12:17 PM, Stephen A Pohl wrote: We will develop[1] a solid 1.0 API around the top features to get the ball rolling and will iterate on these going forward.

Re: What are your use cases for the Touch Bar on the new MacBook Pro?

To build upon the "tab bar" idea: scrolling quickly among my 300+ tabs. On 03/01/17 21:50, sev...@gmail.com wrote: > Off the top of my head ideas: > > Quick-access to the back, forward, refresh, bookmark, share buttons could be > a good. Tab bar might be handy too, so with a touch of my finger

Re: What are your use cases for the Touch Bar on the new MacBook Pro?

Off the top of my head ideas: Quick-access to the back, forward, refresh, bookmark, share buttons could be a good. Tab bar might be handy too, so with a touch of my finger I can go to the tab I want quickly. The bar could change depending on your screen to. If you’re on YouTube/Netflix it

Re: GCC 4.9 now required to build on Linux/Android

On Tue, Jan 3, 2017 at 7:05 AM, Ben Kelly wrote: > FWIW, it seems ./mach bootstrap does not install gcc 4.9 on ubuntu 14.04. It looks like it's not packaged for 14.04; so we'd have to add a ppa to do this prior to 16.04. -r ___

What are your use cases for the Touch Bar on the new MacBook Pro?

We are gathering ideas for possible use cases of the Touch Bar on the new MacBookPro and would like to hear from you! What would improve your workflow? What would help our users? We will develop[1] a solid 1.0 API around the top features to get the ball rolling and will iterate on these going

Re: Intent to implement: Payment Request API

Pada Selasa, 22 November 2016 12.27.52 UTC+7, mcac...@mozilla.com menulis: > ## Summary > The Payment Request API allows web sites selling goods and services to > utilize one or more payment methods through the browser. The browser then > facilitates the payment flow between merchant and user.

Re: GCC 4.9 now required to build on Linux/Android

FWIW, it seems ./mach bootstrap does not install gcc 4.9 on ubuntu 14.04. On Fri, Dec 23, 2016 at 11:08 AM, Nathan Froyd wrote: > Bug 1322792 has landed on inbound, which changes configure to require > GCC 4.9 to build; our automation switched over to GCC 4.9 for our > Linux

Re: Several leak failures have slipped passed continuous integration

Ah, I misunderstood. If the log line is printed or dumped directly to stdout, then the string TEST-UNEXPECTED-FAIL actually will fail the job. It's only if we do log.info('TEST-UNEXPECTED-FAIL ...') that we run into problems. So if you see the string 'TEST-UNEXPECTED-FAIL' somewhere, it isn't

Re: Rust required to build Gecko

On Wed, Dec 21, 2016, at 04:56 PM, Julian Seward wrote: > On 21/12/16 07:55, Jim Blandy wrote: > > The only things I really want anyway are: > > > > mk_add_options MOZ_OBJDIR=obj-bug > > ac_add_options --enable-debug='-g3 -O0 -fno-inline' > > ac_add_options --disable-optimize > > As a side note,

[Firefox Desktop] Issues found: December 26th to December 30th

Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, December 26 - December 30 (week 52). Additional details on the team's priorities last week, as well as the plans for the current week are available at: