Re: Changing the representation of rectangles in platform code

On 2017/02/14 8:37, gsquel...@mozilla.com wrote: On Tuesday, February 14, 2017 at 3:25:05 AM UTC+11, Ehsan Akhgari wrote: On 2017-02-11 3:27 AM, ISHIKAWA,chiaki wrote: On 2017/02/11 7:07, Botond Ballo wrote: On Fri, Feb 10, 2017 at 3:45 PM, Milan Sreckovic wrote: First

Re: Key measurements from memory reports are now shown by crash-stats.m.o

Nice! I see that these fields are available in Super Search already, which is great. This is going to make search queries really powerful. On Tue, Feb 14, 2017, at 12:37 PM, Nicholas Nethercote wrote: > Hi, > > For a long time we have collected a memory report for most crash reports > where the

Re: Intent to implement and ship: only allow Flash on HTTP/HTTPS sites

在 2017/2/14 2:03, Ehsan Akhgari 写道: On 2017-02-13 11:50 AM, 段垚 wrote: 在 2017/2/14 0:24, Ehsan Akhgari 写道: On 2017-02-10 7:51 PM, 段垚 wrote: 在 2017/2/11 2:26, t...@ritter.vg 写道: On Friday, 10 February 2017 08:32:27 UTC-6, Benjamin Smedberg wrote: I thought I enumerated the harm at first,

Key measurements from memory reports are now shown by crash-stats.m.o

Hi, For a long time we have collected a memory report for most crash reports where the crash is caused by an out-of-memory problem. But the memory report data hasn't been incorporated nicely into crash-stats -- you have to save the memory report file to disk and then load it in about:memory to

Re: FYI: We've forked the Breakpad client code

I can review the DWARF related bits in a pinch, too. On Thu, Feb 9, 2017 at 2:04 PM, Mike Hommey wrote: > On Thu, Feb 09, 2017 at 12:41:07PM -0800, Jim Blandy wrote: > > Under the circumstances, I'll volunteer to review, if that's feasible. > > I can too. > > > On Thu, Feb 9,

Re: How to see which parts of Servo are in use?

Yeah, just to elaborate - it's still useful for Servo-only code to show up in searchfox, so that we know about consumers when changing things in the shared style system. On Mon, Feb 13, 2017 at 11:46 AM, Bill McCloskey wrote: > I just filed bug 1339165 to use this

Re: How to see which parts of Servo are in use?

I just filed bug 1339165 to use this categorization in Searchfox. The order of priorities would probably be: normal code test files non-Quantum Servo code generated code -Bill On Mon, Feb 13, 2017 at 5:21 AM, Simon Sapin wrote: > On 13/02/17 13:49, Henri Sivonen wrote: >

Re: Intent to implement and ship: only allow Flash on HTTP/HTTPS sites

On 2017-02-13 11:50 AM, 段垚 wrote: > > > 在 2017/2/14 0:24, Ehsan Akhgari 写道: >> On 2017-02-10 7:51 PM, 段垚 wrote: >>> >>> 在 2017/2/11 2:26, t...@ritter.vg 写道: On Friday, 10 February 2017 08:32:27 UTC-6, Benjamin Smedberg wrote: > I thought I enumerated the harm at first, but I'll

Re: Is there somewhere to get a report of new test failures from a web-platform-tests sync?

On 11/02/17 03:40, Brian Birtles wrote: Yes, I saw that and was very impressed! That's super useful. For Chrome, however, it would be even more useful if we could run those tests with --enable-experimental-web-platform-features. A lot of the Web Animations features we're testing are implemented

Re: Intent to implement and ship: only allow Flash on HTTP/HTTPS sites

在 2017/2/14 0:24, Ehsan Akhgari 写道: On 2017-02-10 7:51 PM, 段垚 wrote: 在 2017/2/11 2:26, t...@ritter.vg 写道: On Friday, 10 February 2017 08:32:27 UTC-6, Benjamin Smedberg wrote: I thought I enumerated the harm at first, but I'll elaborate a little. 1) Flash doesn't know about and breaks our

Re: Intent to implement and ship: only allow Flash on HTTP/HTTPS sites

On 2017-02-10 7:51 PM, 段垚 wrote: > > > 在 2017/2/11 2:26, t...@ritter.vg 写道: >> On Friday, 10 February 2017 08:32:27 UTC-6, Benjamin Smedberg wrote: >>> I thought I enumerated the harm at first, but I'll elaborate a little. >>> >>> 1) Flash doesn't know about and breaks our "current and

Re: Changing the representation of rectangles in platform code

On 2017-02-11 3:27 AM, ISHIKAWA,chiaki wrote: > On 2017/02/11 7:07, Botond Ballo wrote: >> On Fri, Feb 10, 2017 at 3:45 PM, Milan Sreckovic >> wrote: >>> First step needs to happen completely before the second step does, so I >>> guess the danger is that we start and give

Re: How to see which parts of Servo are in use?

On 13/02/17 13:49, Henri Sivonen wrote: A search like https://searchfox.org/mozilla-central/search?q=EncodingRef finds a bunch of stuff that is under servo/components/script/. I gather we don't use that part of Servo in Quantum. Correct? Correct. How does one see which parts of servo/ are

How to see which parts of Servo are in use?

A search like https://searchfox.org/mozilla-central/search?q=EncodingRef finds a bunch of stuff that is under servo/components/script/. I gather we don't use that part of Servo in Quantum. Correct? How does one see which parts of servo/ are actually in use in Quantum? Is there a way to filter out

Marionette tests for Android are Tier-2 now

Over the last couple of weeks I focused my work a bit on getting cleaner jobs for Marionette on Android. Here 9 out of 10 chunks were basically failing all the time. So lots of work was expected. [1] actually tracked everything. To get more passing tests I did not only skip/disable those affected

Re: Please don't add JS implemented telemetry probes to hot code paths. (eom)

For hot code paths, recording every accumulation from C++ directly into Telemetry may also not be ideal. Telemetry::Accumulate() is not very expensive, but it does have costs (locking, lookups). It can e.g. be more efficient to accumulate in a local variable and record the result into Telemetry

[Firefox Desktop] Issues found: February 6th to February 10th

Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *February 6 - February 10* (week 6). Additional details on the team's priorities last week, as well as the plans for the current week are available at:

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

On Tuesday, 3 January 2017 17:17:44 UTC, Stephen A Pohl wrote: > We are gathering ideas for possible use cases of the Touch Bar on the > new MacBookPro and would like to hear from you! What would improve your > workflow? What would help our users? > > We will develop[1] a solid 1.0 API around