Removal of NPAPI plugin support in Firefox 85

Hey all, I am happy to announce that NPAPI plugin support will end in Firefox 85. At the start of the 85 cycle the Plugins Team plans to land changes that disable NPAPI plugin loading and display. We'll also schedule PI testing in both Nightly and Beta on these changes. The initial landing

Re: Software Fallback for Web Render Dog Fooding Phase

On Tuesday, October 27, 2020 at 3:38:32 PM UTC-5, Botond Ballo wrote: > On Tue, Oct 27, 2020 at 4:20 PM Jim Mathies wrote: > > To switch to using software fallback, flip the following prefs - > > > > gfx.webrender.all = true > > gfx.webrender.software = tru

Software Fallback for Web Render Dog Fooding Phase

Hey all, tl/dr; Help us by testing WebRender software fallback, and file bugs against the meta 'sw-wr-dogfood'. WebRender Software Fallback is a project involving the development of a software (vs. accelerated) backend for WebRender. Its purpose is to replace the old graphics pipelines on

Core : Spell checker ownership

Hey all, Somewhere along the way I managed to gain triage ownership of Core:Spell checker. Thing is I've never worked with this code or non-english locale issues which show up. A number of bugs also seem to be tied to DOM related issues related to inline spell checking. Is there someone out

Re: Dropping support for compiling with MSVC in the near future

On Thursday, December 6, 2018 at 5:08:53 PM UTC-6, Gijs Kruitbosch wrote: > Can someone elaborate on what this means for debugging on Windows, and > for our onboarding story on Windows? I just checked to be sure this was all working, and it is. I have VS 2017 and the 'Install Microsoft Child

Re: WebRender on in Firefox Nightly for Windows 10 Nvidia

On Wednesday, September 12, 2018 at 3:07:20 PM UTC-5, Jeff Muizelaar wrote: > In bug 1490742 I have enabled WebRender in Nightly on non-laptop > Windows 10 Nvidia (~17% of our Nightly audience). This is a rewrite of > much the graphics backend in Firefox. We expect some edge-case > regressions,

Looking for testers: Lenovo M30-70 laptop

Hey all, If you have a Lenovo laptop with specs similar to this: Lenovo M30-70 Notebook Intel Core i3-4030U Synaptics ClickPad V1.2 I'd appreciate it if you could try to reproduce Library window scrolling bug 1399126 [1], and if you can, help debug it. Mostly I just want to confirm that in a

RE: More Rust code

What's the debugging situation look like for Windows developers? I've heard it's pretty painful. Can we step through rust code using common tools (WinDBG/Visual Studio)? Jim -Original Message- From: dev-platform [mailto:dev-platform-bounces+jmathies=mozilla@lists.mozilla.org] On

QF bug whiteboard tags

Hey all, The quantum flow project has been filing a lot of bugs lately. I'm curious about two specific whiteboard tags I've seen - [qf:p1] and [qf], can someone explain the differences between these two tags and how this impact the priority of these bugs? Thanks, Jim

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

On Tuesday, January 3, 2017 at 8:38:05 PM UTC-6, Stephen A Pohl wrote: > 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

Re: How should I measure responsiveness?

> * We don't have a "responsiveness index", but several people have > found INPUT_EVENT_RESPONSE_MS useful. INPUT_EVENT_RESPONSE_MS should be of pretty good use although you'll have to figure out how to measure for a short period of time after the dialog is displayed. In non-e10s this

Re: Removing the Chromium event loop

On Wednesday, March 30, 2016 at 1:28:18 PM UTC-5, Kyle Huey wrote: > The other types (TYPE_UI, TYPE_IO, and TYPE_MOZILLA_NONMAINUITHREAD) > involve varying levels of platform specific event loop or API integration > that will probably be more difficult to untangle. They also won't block my >

Flagging Sandboxing bugs

Hey all, Sandboxing is currently enabled for content processes for a couple platforms. If you're curious where a sandbox is running you can check current status at the sandboxing wiki page [1]. The team has a process in place for triaging incoming bugs on a weekly basis. If you think you have

Status: e10s on 45, 46, and 47

Quick update for everyone on the status of e10s: 1) e10s will not be enabled for 45 in the release channel 2) e10s will be enabled for 46 beta through an experiment which will run for the first four to five weeks of the cycle. This experiment will target a larger audience compared to our 45

Re: Talos e10s dashboard

On Friday, February 26, 2016 at 5:58:54 PM UTC-6, William Lachance wrote: > Hey, > > I wrote up a dashboard for tracking the performance delta between > non-e10s and e10s on the Talos tests on nightly: > > https://treeherder.allizom.org/perf.html#/e10s This is great, thanks! A couple

Re: Maintaining the en-US dictionary that ships with Mozilla products

On Tuesday, December 29, 2015 at 2:38:43 PM UTC-6, Ehsan Akhgari wrote: > On 2015-12-28 5:11 PM, Jim Mathies wrote: > > We could research using native spell checking apis if the platform supports > > them. For example Windows added spell checking apis in Windows 8. > > It's

Re: Maintaining the en-US dictionary that ships with Mozilla products

We could research using native spell checking apis if the platform supports them. For example Windows added spell checking apis in Windows 8. https://msdn.microsoft.com/en-us/library/windows/desktop/hh869748%28v=vs.85%29.aspx ___ dev-platform mailing

Re: FYI: e10s will be enabled in beta 44/45

On Sunday, December 13, 2015 at 9:12:59 PM UTC-6, Daniel Veditz wrote: > On Mon, Dec 7, 2015 at 4:36 AM, Kurt Roeckx wrote: > > > On 2015-12-04 19:43, jmath...@mozilla.com wrote: > > > >> Not an issue since initial rollout to beta and release will be to users > >> who do not have

Re: Please help test e10s

Ryan VanderMeulen rya...@gmail.com wrote in message news:y4-dnfcho4l2cghonz2dnuvz_hcdn...@mozilla.org... I won't lie, I'm quite hesitant to dogfood something that has no automated test coverage on my platform. And looking at Holly, I'm not entirely sure *why* m-e10s isn't enabled for

Re: Please help test e10s

/config/mozharness/ -Original Message- From: Gavin Sharp Sent: Tuesday, August 26, 2014 3:04 PM To: Jim Mathies Cc: dev-platform Subject: Re: Please help test e10s I spoke to Mark Hammond about this yesterday. Mark has done some work getting the browser-chrome tests running (bug 932142

Re: You can now get NSPR logs from tryserver mochitest runs

We also have this - https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging#Enable_Logging_for_try_server_runs you might want to update the wiki here if your changes supersede the old way of doing things. Jim -Original Message- From: Honza Bambas Sent: Wednesday,

Re: Tegra build backlog is too big!

Fixing bugs like bug 884972 would probably help quite a bit. Also posting patches with checkin info and marking the bug with checkin-needed so the work lands with other patches. I always try to do this with simple front end patches. Jim Kartikaya Gupta kgu...@mozilla.com wrote in message

Re: Reparenting a XulRunnner window in a Firefox Window

You could do that on Windows, although it would be a bit of a hack. I don't think it's something we would consider checking into the tree. Jim -Original Message- From: Paul Rouget Sent: Wednesday, July 03, 2013 4:10 AM To: Jim Mathies Cc: dev-platform@lists.mozilla.org Subject: Re

Fw: Revamping touch input on Windows

-Original Message- From: Justin Dolske Sent: Sunday, April 21, 2013 9:01 PM Newsgroups: mozilla.dev.platform To: dev-platform@lists.mozilla.org Subject: Re: Revamping touch input on Windows On 4/18/13 5:50 AM, Jim Mathies wrote: One of the concerns here is that since we do not differentiate

Re: Revamping touch input on Windows

Tim Abraldes tabral...@mozilla.com wrote in message news:aamdndrkq8yrr-3mnz2dnuvz_hwdn...@mozilla.org... 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

Re: Preparing for the next windows PGO build memory exhaustion

We also still have bug 845840 - File a support request with ms on our pgo problems. As soon as we sort out the account stuff we can file something. Jim ___ dev-platform mailing list dev-platform@lists.mozilla.org

proposal: replace talos with inline tests

For metrofx we’ve been working on getting omtc and apzc running in the browser. One of the things we need to be able to do is run performance tests that tell us whether or not the work we’re doing is having a positive effect on perf. We currently don’t have automated tests up and running for

Re: proposal: replace talos with inline tests

Good points, comments below. Ed Morley emor...@mozilla.com wrote in message news:mailman.1992.1362404580.24452.dev-platf...@lists.mozilla.org... (CCing auto-to...@mozilla.com) jmaher and jhammel will be able to comment more on the talos specifics, but few thoughts off the top of my head:

Re: proposal: replace talos with inline tests

Boris Zbarsky bzbar...@mit.edu wrote in message news:o7ydnyp6n66okqnmnz2dnuvz_uwdn...@mozilla.org... On 3/4/13 8:15 AM, Jim Mathies wrote: So to work around this I’ve been putting together some basic perf tests I can use to measure performance using the mochitest framework. How are you

Re: Windows 7 Platform Update June 2010 SDK

hi; (cc-ing jimm) The one 32bit binary is used by our users on WinXP, Win7x32, Win8x64. Jimm, you did a bunch of the recent Win8 work, so I guess would have the best context - any compat concerns? tc John. Hmm not sure I can help test. According to that kb article this patch doesn't impact

Re: The future of PGO on Windows

Here are some additional test suites from perftastic for reference. Tp5 from last summer, XP and Win7: http://graphs.mozilla.org/graph.html#tests=[[177,94,12],[177,1,12],[177,94,1],[177,1,1]]sel=nonedisplayrange=365datatype=running Sunspider 2, Win7:

Re: UA string: Touch or Tablet again

On Tuesday, November 13, 2012 4:49:14 AM UTC-6, Jonas Sicking wrote: Note that API detection is only possible client-side. (And using javascript, though this is less of an issue). Websites generally send dramatically different content for touch-based UIs. Different enough that they'd want to

Re: UA string: Touch or Tablet again

I don’t see how this information will be of any use in deciding how to present content, and will likely be used in the wrong way which will break user experiences. We have a related situation with W3C touch event interfaces. Web authors are using their presence as a way to detect mobile

Migrating mozilla-central builds to the Windows 8 SDK

Hey all, Windows 8 metro browser work continues to progress. Within the next couple of months we would like to finish up the process of merging elm over to mozilla-central so we can turn the metro browser bits on in mc nightlies. However before we can do this we'll need to add the latest