Re: Tool for converting C++ standard library naming style to Gecko naming style?

2017-02-23 Thread Henri Sivonen
On Fri, Feb 17, 2017 at 8:54 PM, Birunthan Mohanathas wrote: > On 16 February 2017 at 13:41, Henri Sivonen wrote: >> Is there some kind of tool, similar to ./mach clang-format for >> whitespace, that changes identifies from C++ standard library style to >> Gecko style? > > Yes, clang-tidy has the

Re: Please use Add*VarCache and not Get* when reading pref values in any even possibly warm code paths

2017-02-23 Thread Masayuki Nakano
Do you have any ideas of the cases we should use Add*VarCache? For example, it's bad if using Get* when: * every painting * every mousemove * every user input except mousemove * every focus move * every DOM change * every page load etc. I wonder, if everybody uses Add*VarCache, doesn't it caus

Re: Please use Add*VarCache and not Get* when reading pref values in any even possibly warm code paths

2017-02-23 Thread smaug
On 02/23/2017 11:10 AM, Masayuki Nakano wrote: Do you have any ideas of the cases we should use Add*VarCache? For example, it's bad if using Get* when: * every painting possibly * every mousemove probably * every user input except mousemove well, touchmove is happening a lot too, and pos

Re: Should cheddar-generated headers be checked in?

2017-02-23 Thread Nathan Froyd
On Thu, Feb 23, 2017 at 1:25 AM, Henri Sivonen wrote: >> Alternately you could just generate it at build time, and we could pass >> the path to $(DIST)/include in a special environment variable so you >> could put the header in the right place. > > So just https://doc.rust-lang.org/std/env/fn.var.

Re: Should cheddar-generated headers be checked in?

2017-02-23 Thread Ted Mielczarek
On Thu, Feb 23, 2017, at 08:27 AM, Nathan Froyd wrote: > On Thu, Feb 23, 2017 at 1:25 AM, Henri Sivonen > wrote: > >> Alternately you could just generate it at build time, and we could pass > >> the path to $(DIST)/include in a special environment variable so you > >> could put the header in the r

Re: Should cheddar-generated headers be checked in?

2017-02-23 Thread Ted Mielczarek
On Thu, Feb 23, 2017, at 06:40 AM, Emilio Cobos Álvarez wrote: > On Thu, Feb 23, 2017 at 08:25:30AM +0200, Henri Sivonen wrote: > > On Wed, Feb 22, 2017 at 5:49 PM, Ted Mielczarek wrote: > > > Given that > > > the C API here is under your complete control, it seems like it's > > > possible to gene

Re: Should &&/|| really be at the end of lines?

2017-02-23 Thread Emilio Cobos Álvarez
On Wed, Feb 22, 2017 at 10:27:33AM -0500, Benjamin Smedberg wrote: > On Thu, Feb 16, 2017 at 4:47 PM, wrote: > > > Question of the day: > > When breaking overlong expressions, should &&/|| go at the end or the > > beginning of the line? > > > > TL;DR: Coding style says 'end', I&others think we sh

Intent to implement: Frames timing functions

2017-02-23 Thread Boris Chiou
*Summary*: A frames timing function is a type of timing function that divides the input time into a specified number of intervals of equal length, each of which is associated with an output progress value of increasing value. The difference between a frames timing function and a step timing functio

Re: Should cheddar-generated headers be checked in?

2017-02-23 Thread Emilio Cobos Álvarez
On Thu, Feb 23, 2017 at 08:25:30AM +0200, Henri Sivonen wrote: > On Wed, Feb 22, 2017 at 5:49 PM, Ted Mielczarek wrote: > > Given that > > the C API here is under your complete control, it seems like it's > > possible to generate a cross-platform header > > I believe the header is cross-platform,

Re: Intent to implement: Frames timing functions

2017-02-23 Thread Jeff Muizelaar
The linked bug suggests that Chrome implements this but this email suggests it doesn't. What's the truth? -Jeff On Thu, Feb 23, 2017 at 2:45 AM, Boris Chiou wrote: > *Summary*: > A frames timing function is a type of timing function that divides the > input time into a specified number of inter

Re: New sync IPC messages will require IPC peers' review

2017-02-23 Thread Mike Conley
This is great news. Thanks Kanru. :) On 19/02/2017 9:58 PM, Kan-Ru Chen wrote: > Hi, > > In order to reduce the performance issues caused by sync IPC messages, > we are tracking and removing sync IPCs from the content process or the > UI thread[1]. With bug 1336919 landed[[2] all additions of new

Visual Studio Code recommended extensions

2017-02-23 Thread Marco Bonardo
Hi, I recently started testing VS Code as a replacement for Sublime Text or Atom, and so far the experience has been better than I was expecting. I suspect others of you are doing the same. In bug 1341585, I'm adding .vscode/settings.json to the ignore lists, so that everyone can create his own wo

Re: Visual Studio Code recommended extensions

2017-02-23 Thread Jared Wein
Does the ESLint support hook in to the mozilla-eslint configuration? Can you please update https://developer.mozilla.org/en-US/docs/ESLint or https://wiki.mozilla.org/DevTools/CodingStandards#JS_linting_with_ESLint with any steps required to configure this plugin? Thanks! - jared On Thu, Feb 23,

Re: Visual Studio Code recommended extensions

2017-02-23 Thread Joe Hildebrand
I also like vscode. > On Feb 23, 2017, at 9:48 AM, Marco Bonardo wrote: > > My current list: > // Trim only touched lines. > "NathanRidley.autotrim", > > // Hilight trailing whitespaces. > "ybaumes.highlight-trailing-white-spaces", This one seems a little aggres

Re: Visual Studio Code recommended extensions

2017-02-23 Thread Marco Bonardo
On Thu, Feb 23, 2017 at 6:03 PM, Joe Hildebrand > > // Hilight trailing whitespaces. > > "ybaumes.highlight-trailing-white-spaces", > > This one seems a little aggressive. I'd use it on my code, but on old > broken code, it would be really annoying. > Well, the hilight is very li

Re: Visual Studio Code recommended extensions

2017-02-23 Thread James Graham
On 23/02/17 16:48, Marco Bonardo wrote: // Rust language support. "saviorisdead.RustyCode" I haven't used either (or VS Code much), but my understanding is that is no longer maintained and you should prefer https://github.com/editor-rs/vscode-rust. _

Re: Visual Studio Code recommended extensions

2017-02-23 Thread Marco Bonardo
On Thu, Feb 23, 2017 at 5:56 PM, Jared Wein wrote: > Does the ESLint support hook in to the mozilla-eslint configuration? Can > you please update https://developer.mozilla.org/en-US/docs/ESLint or > https://wiki.mozilla.org/DevTools/CodingStandards#JS_linting_with_ESLint > with any steps required

Re: Visual Studio Code recommended extensions

2017-02-23 Thread Marco Bonardo
On Thu, Feb 23, 2017 at 6:28 PM, James Graham wrote: > On 23/02/17 16:48, Marco Bonardo wrote: > > // Rust language support. >> "saviorisdead.RustyCode" >> > > I haven't used either (or VS Code much), but my understanding is that is > no longer maintained and you should prefer htt

Re: Embeddable Browser

2017-02-23 Thread Rodolpho Porto
Em quarta-feira, 22 de fevereiro de 2017 22:03:41 UTC-3, Myk Melez escreveu: > > Rodolpho Porto > > 2017 February 22 at 03:13 > > > > Hello Myk Melez, > > > > First of all, thank you for your response! > > > > I'll talk about the project, it's a kiosk-style browse

Re: Intent to implement: Frames timing functions

2017-02-23 Thread Brian Birtles
On Fri, Feb 24, 2017 at 12:35 AM, Jeff Muizelaar wrote: > The linked bug suggests that Chrome implements this but this email suggests > it doesn't. What's the truth? There used to be a steps-middle timing function which is what the linked bug originally covered. Chrome implemented it and shipped

Proposed W3C Charter: Web Application Security Working Group

2017-02-23 Thread L. David Baron
The W3C is proposing a revised charter for: Web Application Security (WebAppSec) Working Group https://www.w3.org/2011/webappsec/charter-2017.html https://lists.w3.org/Archives/Public/public-new-work/2017Feb/0014.html Changes from previous charter: https://services.w3.org/htmldiff?doc1