Try-based code coverage results

I don't know how many people follow code-coverage updates in general, but I've produced relatively up-to-date code coverage results based on , and they may be found here: . In contrast to earlier v

Re: Depending on libnotify

Philip Chee writes: > On 02/07/2014 18:13, David Rajchenbach-Teller wrote: > We had libnotify support but this was removed from the tree on the > grounds that it didn't suit our needs. I don't think those were the grounds. AIUI it was just that people didn't want to put effort into a lower prior

Interfaces nsIX509Cert2/nsIX509Cert3 and nsIX509CertDB2 merged with nsIX509Cert/nsIX509CertDB respectively.

Hi All, Interfaces nsIX509Cert2, and nsIX509Cert3 have been merged with nsIX509Cert. Similarly, nsIX509CertDB2 has been merged with nsIX509CertDB. Hence, these are the only two ( nsIX509Cert and nsIX509CertDB) which should be used going forward. All required functions can only be accessed throu

Re: Reordering opened windows

It seems like the solution to this would be for the first opened window to trigger the session restore, and the session restore process goes like this: 1. Open additional win32 windows in the correct order 2. Load the basic browser XUL into each window 3. Bring the 'priority load'/active window to

Re: Reordering opened windows

David Rajchenbach-Teller wrote: We are considering redesigning slightly how windows are reopened by Session Restore, to ensure that most recently used windows are loaded first. I can't quite tell from your phrasing whether the bottleneck here is the time it takes to open windows. I'm assumi