Re: Changes to tab min-width

2017-10-06 Thread Nicholas Nethercote
On Sat, Oct 7, 2017 at 9:40 AM, Mike Hommey wrote: > Side note: it's sad that side-bar based tab addons now have to waste a > large portion of vertical space because of the (large) side-bar header. > Plus, they can't push the toolbar like they used to, taking the whole > height of the window. >

Re: Changes to tab min-width

2017-10-06 Thread Mike Hommey
On Fri, Oct 06, 2017 at 05:40:13PM +0100, Jonathan Kew wrote: > On 06/10/2017 17:05, Boris Zbarsky wrote: > > On 10/3/17 5:18 PM, Boris Zbarsky wrote: > > > 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 > > > ye

Re: Changes to tab min-width

2017-10-06 Thread Daniel Veditz
On Fri, Oct 6, 2017 at 12:15 PM, Randell Jesup wrote: > There's "publish an extension that > ​ ​ > lets you fiddle the width" (doable today). ​WebExtensions can't manipulate prefs other than the ones explicitly exposed via a WebExtension API. Only "system add-ons" have that power now. yes! I

Re: Changes to tab min-width

2017-10-06 Thread Randell Jesup
>On Fri, Oct 6, 2017 at 12:57 AM, Lars Hansen wrote: > >> even if I don't exactly remember the ID I'm looking for I can narrow >> it down to one or two tabs and then hover if I need to. >> >> Many other sites also have tabs that can be distinguished >> from the first few letters - if you can see t

Re: Changes to tab min-width

2017-10-06 Thread Daniel Veditz
On Fri, Oct 6, 2017 at 12:57 AM, Lars Hansen wrote: > even if I don't exactly remember the > ​ ​ > ID I'm looking for I can narrow it down to one or two tabs and then hover > ​ ​ > if I need to. > ​ ​ > Many other sites also have tabs that can be distinguished > ​ ​ > from the first few letters -

Re: Changes to tab min-width

2017-10-06 Thread Eric Rahm
I settled on 110px as well for the same reason. -e On Fri, Oct 6, 2017 at 9:05 AM, Boris Zbarsky wrote: > On 10/3/17 5:18 PM, Boris Zbarsky wrote: > >> 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)... >> >

Re: Changes to tab min-width

2017-10-06 Thread Jonathan Kew
On 06/10/2017 17:05, Boris Zbarsky wrote: On 10/3/17 5:18 PM, Boris Zbarsky wrote: 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)... OK, now I have had a chance to try it. When set to the new 50px default,

Re: Changes to tab min-width

2017-10-06 Thread Boris Zbarsky
On 10/3/17 5:18 PM, Boris Zbarsky wrote: 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)... OK, now I have had a chance to try it. When set to the new 50px default, I see 1 letter of title or less (less, bec

Re: Changes to tab min-width

2017-10-06 Thread Gabor Krizsanits
On Fri, Oct 6, 2017 at 3:52 PM, Nicolas B. Pierron < nicolas.b.pier...@mozilla.com> wrote: > > I will add that 91% of the session on release have 12 or fewer tabs, and > thus would not be concerned at all by these changes. So among the 9% > remaining, 33% of them are using 20 tabs or fewer, and 6

Re: C++ function that the optimizer won't eliminate

2017-10-06 Thread Botond Ballo
Not immediately useful to us, but there is a C++ standards proposal in the works for a standard library function along these lines: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0412r0.html Cheers, Botond ___ dev-platform mailing list dev-pla

Re: Changes to tab min-width

2017-10-06 Thread Boris Zbarsky
On 10/6/17 9:52 AM, Nicolas B. Pierron wrote: I will add that 91% of the session on release have 12 or fewer tabs, and thus would not be concerned at all by these changes. Do we actually know that? As I said upthread, at the 100px tab width my tabs start to scroll when adding the 9th tab. -

Re: C++ function that the optimizer won't eliminate

2017-10-06 Thread David Major
I bet Google Benchmark will have what you want. As a first guess, maybe this? https://github.com/google/benchmark/blob/master/include/benchmark/benchmark.h#L297 (And if godbolt says they are wrong, please send them a PR :)) On Fri, Oct 6, 2017 at 9:16 AM, Gabriele Svelto wrote: > On 06/10/201

Re: Changes to tab min-width

2017-10-06 Thread Nicolas B. Pierron
On 10/05/2017 01:34 PM, Chris Hutten-Czapski wrote: I prefer the old behaviour, but I don't have a strong opinion on the matter. I think it's because I'm used to tab navigation by keyboard shortcut more than by mouse. I rearrange tabs so that they're close together. For everyone curious about ho

Re: C++ function that the optimizer won't eliminate

2017-10-06 Thread Gabriele Svelto
On 06/10/2017 11:00, Henri Sivonen wrote: > Do we already have a C++ analog of Rust's test::black_box() function? > I.e. a function that just passes through a value but taints it in such > a way that the optimizer can't figure out that there are no side > effects. (For the purpose of ensuring that

Re: C++ function that the optimizer won't eliminate

2017-10-06 Thread Nathan Froyd
On Fri, Oct 6, 2017 at 5:00 AM, Henri Sivonen wrote: > Do we already have a C++ analog of Rust's test::black_box() function? We do not. > Specifically, this isn't the answer for GCC: > void* black_box(void* foo) { > asm ("":"=r" (foo): "r" (foo):"memory"); > return foo; > } Can you provide

Re: C++ function that the optimizer won't eliminate

2017-10-06 Thread Boris Zbarsky
On 10/6/17 5:00 AM, Henri Sivonen wrote: If we don't have one, how should one be written so that it works in GCC, clang and MSVC? Are you OK with it being restricted to a single thread? If so, would something like this work? mutable void* taint; void* black_box(void* foo) { taint =

C++ function that the optimizer won't eliminate

2017-10-06 Thread Henri Sivonen
Do we already have a C++ analog of Rust's test::black_box() function? I.e. a function that just passes through a value but taints it in such a way that the optimizer can't figure out that there are no side effects. (For the purpose of ensuring that the compiler can't eliminate computation that's be

Re: Intent to ship: Throttling timeouts in background using execution budget.

2017-10-06 Thread Andreas Farre
Yes, there are related telemetry probes, but I've recently convinced myself that they won't be able to clearly detect budget throttling. The probe is TIMEOUT_EXECUTION_BG_MS, and the reason for it not working is that it accumulates execution over one second, which just happens to be the time of the

Re: Changes to tab min-width

2017-10-06 Thread Lars Hansen
On Wed, Oct 4, 2017 at 6:15 PM, Jeff Griffiths wrote: > On Tue, Oct 3, 2017 at 6:33 PM, Brendan Barnwell > wrote: > ... > > > The difference between 12 and 24 tabs is meaningless. My usage > of > > Firefox involves large numbers of tabs, frequently exceeding 1000. This > > use case is

Re: Changes to tab min-width

2017-10-06 Thread bruno ais
Maybe if you use browser.tabs.tabMinWidth = 80 instead, it can make it work better than 75 because, with 75, it still loses some extra information. On Fri, Oct 6, 2017 at 2:20 AM, Ehsan Akhgari wrote: > On 10/04/2017 12:43 PM, Jeff Griffiths wrote: > >> Om my system ( retina macbook pro ) 70 is

Re: Changes to tab min-width

2017-10-06 Thread Gian-Carlo Pascutto
On 03-10-17 22:36, Jeff Griffiths wrote: > 2. if you prefer a value for this pref different than 50 or 100, what > is it? Why? 80 gives about 3.5 to 4.5 characters of context, which seems to be enough in most cases. 70 is definitely too tiny, 75 is on the edge (I could probably live with it). 80 m