Telemetry Histogram Expiry
The following histograms will be expiring on 2017-04-17, and should be removed from the codebase, or have their expiry versions updated: * REMOTE_JAR_PROTOCOL_USED expires in version 55.0a1 (watched by dev-platform@lists.mozilla.org) - Remote JAR protocol usage This is an automated message sent by Cerberus. See https://github.com/mozilla/cerberus for details and source code. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: All the processes
We also have the Gecko Media Plugin process type. It's not the same as Flash plugin process. There are at least one per origin doing EME and one shared by all users of WebRTC that need to encode/decode H.264. The media playback team are also working on moving the code that interacts with the platforms' audio subsystem into its own process, but that project has only recently started. cpearce. On Saturday, March 4, 2017 at 1:16:00 PM UTC+13, Nicholas Nethercote wrote: > Hi, > > I want to understand all the different processes that we can and will have > in Firefox. Here's a list I constructed off the top of my head. > > - main process > > - content process(es): 1 on release for most users; 2 on Nightly > > - plugin process: just for Flash now? > > - gfx compositor process (bug 1264543, in Fx53) > > - file:// URL access process (bug 1147911, in Fx53) > > IIRC there was a proposal for a thumbnail generation process a while back > but judging by bug 1187441 that was scrapped. > > Do I have any of these details wrong? Have I missed any? > > Thanks. > > Nick ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Revocation protocol idea
Hi, folks. Some time ago, I've started to think about an idea to experiment with new powerful Web APIs: a sort of "deceptive site" database for harmful uses of browsers APIs. I've been curating that idea and come up with the concept of a "revocation protocol" to revoke user granted permissions for origins abusing those APIs. I published the idea on GitHub [1] and I was wondering about the utility and feasibility of such a system so I would thank any feedback you want to provide. I hope it will be of interest for you. [1] https://github.com/delapuente/revocation-protocol -- ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
