Re: Changes to tab min-width

2017-10-10 Thread Jeff Griffiths
On Oct 6, 2017 07:50, "Boris Zbarsky" wrote: 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

Re: Changes to tab min-width

2017-10-04 Thread Jeff Griffiths
until 2 tabs have been closed! ) - count the number of tabs opened - open chrome and open that number of tabs - compare the utility of each browser Jeff On Wed, Oct 4, 2017 at 9:37 AM, Marco Bonardo wrote: > On Tue, Oct 3, 2017 at 10:36 PM, Jeff Griffiths > wrote: > > 1. d

Re: Changes to tab min-width

2017-10-04 Thread Jeff Griffiths
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 quite manageable with a combination of extensions (e.g., Tab > Mix Plus

Changes to tab min-width

2017-10-03 Thread Jeff Griffiths
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 set

E10S and Dom Inspector

2015-12-14 Thread Jeff Griffiths
( re-posting this from firefox-dev at dcamp's suggestion, sorry if this feels like a duplicate thread to you ) The e10s team looked at bug 1078121[1] this morning and asked how concerned I am about it. I responded in comment 7 ( link below ) and I *think* my workarounds are reasonable, however I w

Re: recording use counters for web features

2015-08-24 Thread Jeff Griffiths
This looks like it will be amazing. I would like to talk about expanding css coverage as much as possible, as a followup to the initial work. On Thu, Aug 20, 2015 at 9:38 AM, Nathan Froyd wrote: > [Responding to the list this time...] > > On Thu, Aug 20, 2015 at 4:05 AM, Patrick Brosset > wrote:

Re: Intent to implement: Moving DevTools to top level /devtools directory

2015-07-23 Thread Jeff Griffiths
On Thu, Jul 23, 2015 at 11:43 AM, J. Ryan Stinnett wrote: > On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget wrote: >> I guess by moving things to /devtools/, you also want to update the >> URLs to chrome://devtools/content. >> So then, we can compile and open the devtools with non-firefox builds >>