Re: Coding style: Naming parameters in lambda expressions

2019-09-05 Thread Emilio Cobos Álvarez
Yeah, let's not add a new prefix please. I don't like aFoo either, though it's everywhere so consistency is better than nothing :/. That being said, it shouldn't be hard to write some clang plugin or such that automatically renames function arguments to stop using aFoo, should we want to do

Re: Coding style: Naming parameters in lambda expressions

2019-09-05 Thread Jeff Gilbert
I remain against aFoo style. I still think it's low-signal-high-noise, and doesn't provide value that modern syntax highlighting doesn't provide for those who find it useful. I'm absolutely opposed to adding a new prefix. That would be moving even further down the path of our proprietary

Re: Nika Layzell and Kris Maglione are now XPCOM peers

2019-09-05 Thread Kris Maglione
On Wed, Sep 4, 2019, 11:33 Nathan Froyd Kris noticed that Nika was going to become an XPCOM peer and, not > wanting to be left out, volunteered (yes, really). Kris has worked on > modernizing the component manager and various thread-related > improvements. > To be clear, I volunteered because

Re: Intent to Ship - Support XCTO: nosniff for navigations

2019-09-05 Thread Boris Zbarsky
On 9/5/19 9:20 AM, Sebastian Streich wrote: In Firefox 70 I intend to enable nosniff support for page navigations by default. We're still doing stream converters for navigations even if that header is sent. Is that intended? I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1579176 to

Re: Intent to Ship - Support XCTO: nosniff for navigations

2019-09-05 Thread Daniel Veditz
On Thu, Sep 5, 2019 at 6:21 AM Sebastian Streich wrote: > Link to standard: > https://fetch.spec.whatwg.org/#x-content-type-options-header That bit of the standard doesn't describe this behavior--it still only talks about scripts and style. Is there an issue or PR to update the spec to

Intent to Ship - Support XCTO: nosniff for navigations

2019-09-05 Thread Sebastian Streich
Currently the Support for “X-Content-Type-Options: nosniff“ is limited to CSS and JS resources. In Firefox 70 I intend to enable nosniff support for page navigations by default. If a server's response does not include any mime-type but sets the response header "XCTO: nosniff" then Firefox will

Coding style: Naming parameters in lambda expressions

2019-09-05 Thread Simon Giesecke
Hi, we encountered the question of how to name parameters in lambda expressions. For regular functions, the coding style implies that parameter naming should use camelCase with an "a" prefix, and this is also widely done this way. The coding style does not say anything specifically concerning