Re: The e10s throbber

2015-04-08 Thread Gijs Kruitbosch
On 07/04/2015 23:41, Robert O'Callahan wrote: On Wed, Apr 8, 2015 at 6:27 AM, Gavin Sharp ga...@gavinsharp.com wrote: We don't have telemetry yet. I've done some measurements and haven't found any cases where tab switching consistently takes longer in e10s. However, it's certainly possible

Re: The e10s throbber

2015-04-08 Thread Nick Fitzgerald
Yes they are built on the same SPS profiler backend. However, the gecko profiler addon will do things the builtin devtools can't, like open a shell and call `atos` to symbolicate C++ function addresses. See https://bugzilla.mozilla.org/show_bug.cgi?id=1132529 for some context. For the time

Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Seth Fowler
I sometimes ask users to test a try build to verify that the build fixes their problem. This is an important tool, especially when the problem is hard to reproduce or when the definition of “fix” is a bit nebulous (as it sometimes is in performance-related bugs). However, I don’t want to run

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Mike Hoye
On 2015-04-08 3:08 PM, Seth Fowler wrote: Can we do this? Any better ideas? I filed 1013371 a while back asking for something not quite identical that might meet your needs. Automatically create clean profiles when -P specifies nonexistent profile. - mhoye

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread L. David Baron
On Wednesday 2015-04-08 12:08 -0700, Seth Fowler wrote: I think one way we could reduce the burden on users would be to just make try builds default to a different profile than channel builds. Is there a simple patch one could push to change this default, and just include on any try pushes

Re: IndexedDB transactions are no longer durable by default, and other changes

2015-04-08 Thread Botond Ballo
2. The the schema version for all databases has changed, so once you open a database on trunk builds and it upgrades you will not be able to open that same database in an aurora/beta/release build. Have we considered issuing a warning saying that after upgrading the profile, it will not be

Re: IndexedDB transactions are no longer durable by default, and other changes

2015-04-08 Thread J. Ryan Stinnett
On Wed, Apr 8, 2015 at 2:30 PM, Botond Ballo bba...@mozilla.com wrote: Have we considered issuing a warning saying that after upgrading the profile, it will not be compatible with older versions? I would really like to have something like this. WebIDE makes use of IndexedDB today, and it seems

Re: IndexedDB transactions are no longer durable by default, and other changes

2015-04-08 Thread Jan Varga
This is a good idea. On 08/04/15 21:30, Botond Ballo wrote: 2. The the schema version for all databases has changed, so once you open a database on trunk builds and it upgrades you will not be able to open that same database in an aurora/beta/release build. Have we considered issuing a

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Gavin Sharp
I think you can get this fairly easily by just changing one of the values (Vendor or Name) in build/application.ini such that a different profile folder is used. Gavin On Wed, Apr 8, 2015 at 12:28 PM, L. David Baron dba...@dbaron.org wrote: On Wednesday 2015-04-08 12:08 -0700, Seth Fowler

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Jonathan Griffin
There is also an old, unmaintained GUI for managing profiles: https://developer.mozilla.org/en-US/docs/Profile_Manager It still works, although there are a few bugs. It may be an improvement over command-line arguments for less technical users. Jonathan On Wed, Apr 8, 2015 at 12:49 PM, Gavin

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Dale Harvey
+1000 I am constantly killing my profile by downgrading it when I need to test something on Firefox Stable. Switching between Chrome releases couldnt be easier but even as a Firefox Dev switching between profiles when testing a different version is a nightmare, I cant imagine how unfriendly it is

Intent to Implement and Ship: UI Events (formerly DOM Level 3 Events) EventModifierInit

2015-04-08 Thread Masayuki Nakano
EventModifierInit is a dictionary to initialize modifier state at creating untrusted event. This allows to initialize AltGraph, CapsLock, Fn, FnLock, Hyper, NumLock, OS, ScrollLock, Super, Symbol and SymboleLock state of creating events and it has been no way to initialize them. Currently,

Re: Is MOZ_SHARK still used?

2015-04-08 Thread Cameron Kaiser
On 4/6/15 8:11 AM, Eric Shepherd (Sheppy) wrote: Is it worth talking to someone from the TenFourFox project (http://www.floodgap.com/software/tenfourfox/) to see if they have an opinion on this? They may be using Shark still for their debugging and testing processes. I responded in the bug,

W3C Proposed Recommendation: HTML5 Web Messaging

2015-04-08 Thread L. David Baron
W3C recently published the following proposed recommendation (the stage before W3C's final stage, Recommendation): HTML5 Web Messaging http://www.w3.org/TR/webmessaging/ There's a call for review to W3C member companies (of which Mozilla is one) open until Tuesday, May 5. If there are

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Seth Fowler
My concern with an approach like this is that it’s opt-in, and developers may not necessarily keep this issue in mind every time they offer a build for someone to try. I’ve seen other developers suggest that users experiment with try builds, but I’m not sure how widespread it is. Probably

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Nicholas Alexander
On Wed, Apr 8, 2015 at 4:06 PM, Mike Hommey m...@glandium.org wrote: On Wed, Apr 08, 2015 at 12:08:27PM -0700, Seth Fowler wrote: I sometimes ask users to test a try build to verify that the build fixes their problem. This is an important tool, especially when the problem is hard to

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Francois Marier
On 09/04/15 15:39, Seth Fowler wrote: Sounds like yet another reason to build support and UI for this stuff directly into the browser. On that note, Bram from UX has some ideas about what it could look like: https://wiki.mozilla.org/Security/Contextual_Identity_Project/User_Profiles

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Seth Fowler
On Apr 8, 2015, at 8:37 PM, Nicholas Alexander nalexan...@mozilla.com wrote: It's quite important for Firefox for Android that try builds look and behave exactly like Nightly builds. On Android, it's not really possible to move/copy/duplicate profiles, and it's rocket science to do it

HTTP/1.1 Multiplexing

2015-04-08 Thread max . bruce12
I wrote a very simple addition to HTTP/1.1 in which I plan to draft as a RFC soon, which allows multiplexing, prevents HOL blocking, and allows server pushing in HTTP/1.1. HPack could also be incorporated, via negotiation. The idea? A request begins by adding a header: X-Req-ID, set to a

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Nicholas Alexander
Hi Seth, others, On Wed, Apr 8, 2015 at 12:08 PM, Seth Fowler s...@mozilla.com wrote: I sometimes ask users to test a try build to verify that the build fixes their problem. This is an important tool, especially when the problem is hard to reproduce or when the definition of “fix” is a bit

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Xidorn Quan
On Thu, Apr 9, 2015 at 9:00 AM, Gavin Sharp ga...@gavinsharp.com wrote: I think that's overthinking it - I doubt Seth was intending to distribute these builds widely or frequently. A few leftover profile files won't hurt anyone :) It wouldn't be distributed widely, but could be frequently

Intent to ship: Identity provider proxy for WebRTC

2015-04-08 Thread Martin Thomson
As of 2015-04-15 I intend to turn identity for WebRTC on by default. It has been developed behind the media.peerconnection.identity.enabled preference. Firefox will be the first to implement this; I have only informal promises from Google to implement once we ship. This feature is the mutual

Re: Intent to ship: Identity provider proxy for WebRTC

2015-04-08 Thread Martin Thomson
My bad, here's the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1152538 On Wed, Apr 8, 2015 at 2:11 PM, Martin Thomson m...@mozilla.com wrote: As of 2015-04-15 I intend to turn identity for WebRTC on by default. It has been developed behind the media.peerconnection.identity.enabled

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Mike Hommey
On Thu, Apr 09, 2015 at 08:48:32AM +1200, Xidorn Quan wrote: On Thu, Apr 9, 2015 at 7:49 AM, Gavin Sharp ga...@gavinsharp.com wrote: I think you can get this fairly easily by just changing one of the values (Vendor or Name) in build/application.ini such that a different profile folder is

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Gavin Sharp
I think that's overthinking it - I doubt Seth was intending to distribute these builds widely or frequently. A few leftover profile files won't hurt anyone :) Gavin On Apr 8, 2015, at 1:48 PM, Xidorn Quan quanxunz...@gmail.com wrote: On Thu, Apr 9, 2015 at 7:49 AM, Gavin Sharp

Re: Can we make try builds default to a different profile than Nightly/Aurora/Beta/Release builds?

2015-04-08 Thread Mike Hommey
On Wed, Apr 08, 2015 at 12:08:27PM -0700, Seth Fowler wrote: I sometimes ask users to test a try build to verify that the build fixes their problem. This is an important tool, especially when the problem is hard to reproduce or when the definition of “fix” is a bit nebulous (as it sometimes is