Re: How useful is the WinSock LSP field in crash reports?

I do use it - but LSPs obviously cause the networking team more trouble than other folks. I have no objection if the UI just wants to move it to somewhere less obtrusive though - as long as its there. On Mon, Jul 25, 2016 at 6:29 PM, Aaron Klotz wrote: > On 7/25/2016 12:20

Re: How to measure performance impact of l10n on UI

> If I understand correctly, firstPaint from getStartupInfo will tell me when > the first paint of the window occured. > > But since I'm operating in a document (I'm working on about:support > document), I'm looking for the firstPaint of the document, not the whole > browser window. > > So,

Re: Intent to implement: CSS Houdini - Properties & Values API Level 1

> On Jul 25, 2016, at 10:47 AM, James Graham wrote: > > On 25/07/16 16:48, Daniel Holbert wrote: >> On 07/25/2016 07:11 AM, Ms2ger wrote: >>> Are there automated tests that will be shared with other vendors (and >>> Servo)? >> >> There are some reftests on the bug [2]

Re: Intent to implement: CSS Houdini - Properties & Values API Level 1

On 25/07/16 16:48, Daniel Holbert wrote: On 07/25/2016 07:11 AM, Ms2ger wrote: Hey Jonathan, [...] Do we know how other vendors feel about this? Sentiment seems to be positive. Browser vendors are collaborating on developing the Houdini specs, and I haven't heard any serious reservations

Re: How useful is the WinSock LSP field in crash reports?

filed: https://bugzilla.mozilla.org/show_bug.cgi?id=1289167 On Mon, Jul 25, 2016 at 9:29 AM, Aaron Klotz wrote: > On 7/25/2016 12:20 AM, Nicholas Nethercote wrote: >> >> I suspect it is rare for this field to be useful. (I've never found it >> useful.) It is also long,

Re: How useful is the WinSock LSP field in crash reports?

On 7/25/2016 12:20 AM, Nicholas Nethercote wrote: I suspect it is rare for this field to be useful. (I've never found it useful.) It is also long, typically dozens of lines, and typically accounts for a quarter or more of the space taken up by the fields in the "Details" tab. I use it when

Re: Intent to implement: CSS Houdini - Properties & Values API Level 1

On 07/25/2016 07:11 AM, Ms2ger wrote: > Hey Jonathan, [...] > Do we know how other vendors feel about this? Sentiment seems to be positive. Browser vendors are collaborating on developing the Houdini specs, and I haven't heard any serious reservations on this spec. (This is among the more

Re: PSA - With e10s enabled, initial browser in new windows will soon be remote by default

Hey bkelly, Do we still kill the child process if the last content tab is closed? Yes we do. When a TabParent gets destroyed, it calls into here: http://searchfox.org/mozilla-central/rev/336105a0de49f41a2cc203db7b7ee7266d0d558b/dom/ipc/ContentParent.cpp#2074 That code checks to see if any

Re: PSA - With e10s enabled, initial browser in new windows will soon be remote by default

Mike, Do we still kill the child process if the last content tab is closed? For example, close all tabs in all windows except for an about:memory tab or something. Or do we keep the child process alive as long as the browser.xul window is alive? Keeping the process alive would actually make a

Re: PSA - With e10s enabled, initial browser in new windows will soon be remote by default

After much toil, this has finally landed on central. Hopefully it sticks. Big thanks to all of my reviewers - especially smaug, who reviewed the bulk of the weirder stuff. -Mike On 9 June 2016 at 14:21, Mike Conley wrote: > If you don’t write tests that open browser

Re: Intent to implement: CSS Houdini - Properties & Values API Level 1

Hey Jonathan, On 22/07/16 23:26, Jonathan Chan wrote: > Summary: > > Allow web developers to register typed and animatable custom CSS properties > through JavaScript with configurable inheritance and initial values. > > Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1273706 > Link to