Re: Intent to implement and ship: CSP exemptions for content injected by privileged callers

On 10/2/17 9:50 PM, Kris Maglione wrote: For the pretty simple micro-benchmark below, here are the in-document and out-of-document numbers for three runs without the subject principal: Sorry, I should have been clearer: I meant numbers for "inserted into the document" and "not inserted into

Re: Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

Wow, this is great! I just ran into this problem a week ago and it was quite annoying to work around. Thanks for fixing it. :-) bholley On Tue, Oct 3, 2017 at 4:15 PM, Matthew N. wrote: > With bug 1401343 > fixed,

Re: Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

On 2017-10-03 5:44 PM, Boris Zbarsky wrote: On 10/3/17 7:15 PM, Matthew N. wrote: For those of you who don't know, when the "devtools.chrome.enabled" pref is true the Web Developer > Browser Content Toolbox opens a toolbox targeting the content process that the selected tab is loaded in.

Re: Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

On 10/3/17 7:15 PM, Matthew N. wrote: For those of you who don't know, when the "devtools.chrome.enabled" pref is true the Web Developer > Browser Content Toolbox opens a toolbox targeting the content process that the selected tab is loaded in. Matt, Do you know whether this starts a new

Re: Intent to unship: :-moz-system-metric pseudo-class and media queries in content pages.

On Sat, Sep 2, 2017, at 06:06 AM, Emilio Cobos Álvarez wrote: > Hi dev-platform@, > > I'd like to unship access to the :-moz-system-metric pseudo-class, and > the system metric media queries, from content pages. I just filed > for that. > >

Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

With bug 1401343 fixed, `TabChildGlobal`s for the attached content process are exposed via a `tabs` getter in the Browser Content Toolbox's console tab. This makes it much easier to inspect a remote tab's state or to access privileged APIs

Re: Changes to tab min-width

On 2017-10-03 2:18 PM, Boris Zbarsky wrote: Right now, at 60px, I can see 7-10 chars in a tab title.  This is sometimes (but not always) enough for me to make sense of what I'm looking at when the favicon is not helpful.  For example, for bugzilla bugs I can see the whole bug number. In the

Re: --verify option added to mochitest, reftest, xpcshell test harnesses

On Tue, Oct 3, 2017 at 1:05 PM, Andrew Halberstadt wrote: > This is really great Geoff! Hopefully it can cut down the number of new > intermittents we introduce to the tree. Do you know if orangefactor or > ActiveData can track the rate of new incoming intermittents?

Re: Changes to tab min-width

Jeff Griffiths wrote: 1. do you prefer the existing behaviour or the new behaviour? I prefer the new behavior. 2. if you prefer a value for this pref different than 50 or 100, what is it? Why? I prefer a value of 0 (i.e. truly infinite tabs, never scrolling), because I distinguish tabs by

Re: Changes to tab min-width

On 10/3/17 4:36 PM, Jeff Griffiths wrote: 2. it sets the default value of the tab to 50, previously this value was hard-coded at 100. Jeff, So just to make sure I understand the change (and this is a theoretical point, because I haven't had a chance to try the change yet)... Right now, the

Re: Intent to implement: CSS media queries, interaction media features

> Will those measures be part of the work done (enabled only when > privacy.resistFingerprinting is set)? If we want them to be, sure. I don't mind adding a patch to do so as part of the initial landing rather than a follow-up. Bear in mind that I'm operating on the presumption that we would

Re: Intent to implement: CSS media queries, interaction media features

On 10/03/2017 10:12 PM, Thomas Wisniewski wrote:> Security & Privacy Concerns: this exposes whether the user has pointer that > is finely controlled like a mouse, or more coarse-grained like a > touchscreen (or no pointer at all). It also exposes whether they have a > pointer capable of "hover"

Re: Intent to implement: CSS media queries, interaction media features

On Tue, Oct 3, 2017 at 3:12 PM, Thomas Wisniewski wrote: > Security & Privacy Concerns: this exposes whether the user has pointer that > is finely controlled like a mouse, or more coarse-grained like a > touchscreen (or no pointer at all). It also exposes whether they have

Changes to tab min-width

Hi! tl;dr we changed the default pixel value at which we overflow tabs, and I want your feedback. We just added a change to m-c[1] that does to things: 1. it reintroduces an old preference 'browser.tabs.tabMinWidth' that contains a pixel value that controls the minimum width of a tab. 2. it

Intent to implement: CSS media queries, interaction media features

Summary: Implement the CSS features [any-]pointer:{none|coarse|fine} and [any-]hover:{none|hover} in a manner that is compatible with Blink. These features are implemented in all other major engines including Edge, and sites like Gmail are now using them. Our lack of support for these features has

Re: --verify option added to mochitest, reftest, xpcshell test harnesses

This is really great Geoff! Hopefully it can cut down the number of new intermittents we introduce to the tree. Do you know if orangefactor or ActiveData can track the rate of new incoming intermittents? Would be neat to see how much of an impact this tool has on that. On Mon, Oct 2, 2017 at 1:08

Re: Containers graduation from Test Pilot - we still care about 57+

Just to close the loop on this thread, in 57 this will no longer disable multi-e10s. https://bugzilla.mozilla.org/show_bug.cgi?id=1404098 Thanks for the heads up Ben. On 27 September 2017 at 10:53, Ben Kelly wrote: > It disables multi-e10s. Forced to one content process. >

Re: --verify option added to mochitest, reftest, xpcshell test harnesses

This is super cool! Thanks Geoffrey! On 2017-10-02 1:08 PM, Geoffrey Brown wrote: > The mochitest, reftest, and xpcshell test harnesses now support a > --verify option. For example: > > mach mochitest > docshell/test/test_anchor_scroll_after_document_open.html --verify > > In verify mode, the

Pre-commit hook for adding new FTL localization files

Hi all, tl;dr - This will almost certainly not affect your work. We're adding a temporary pre-commit hook that requires L10n Drivers to r+ any patches that touch .ftl files. As the waters calm down after 57 cycle, we're getting ready to start enabling the new localization API in Gecko.