On 05-10-17 22:46, Daniel Veditz wrote:
> On Thu, Oct 5, 2017 at 1:07 PM, Gian-Carlo Pascutto wrote:
>
>> Is it technically difficult to try the technique of starting with 50px,
>> and switching to 100px as soon as 50px wouldn't fit anyway?
>
>
> Shrinking until they suddenly embiggen and push
On 10/04/2017 12:43 PM, Jeff Griffiths wrote:
Om my system ( retina macbook pro ) 70 is starting to look like a
better compromise for tab readability.
I think 70 is better than 50, but I noticed that if a foreground tab
starts to play audio and we need to show the audio icon alongside the
tab c
On Thu, Oct 5, 2017 at 1:07 PM, Gian-Carlo Pascutto wrote:
> Is it technically difficult to try the technique of starting with 50px,
> and switching to 100px as soon as 50px wouldn't fit anyway?
Shrinking until they suddenly embiggen and push half your tabs out of
sight is going to annoy plent
On 4/10/2017 18:15, Jeff Griffiths wrote:
> The feedback I am going to find actionable here is, which
> setting value of this preference do you find most useful.
Jeff,
I've read through all the responses here, and I've seen several people
point out the same problem I did: we're getting the worst
On 5/10/2017 19:35, Boris Zbarsky wrote:
> On 10/5/17 1:05 PM, Gian-Carlo Pascutto wrote:
>> [1] I'm sure users that have been conditioned that there exists only a
>> single search engine are going to be confused by the choice that it
>> offers. Maybe we should remove the search box and switch to a
On 10/5/17 1:05 PM, Gian-Carlo Pascutto wrote:
[1] I'm sure users that have been conditioned that there exists only a
single search engine are going to be confused by the choice that it
offers. Maybe we should remove the search box and switch to an Omnibar.
Um... haven't we? Current nightlies
On 03-10-17 22:36, Jeff Griffiths wrote:
> We did this based on some early feedback from a few different sources
> that people coming from chrome
That's rather ironic. I have always thought that one reason why Chrome
uses these uselessly-tiny tabs is to *discourage* users from hoarding a
lot of t
The PerformanceResourceTiming API has had a `workerStart` value specified
for a couple years now. Its defined to represent the time when we trigger
a service worker FetchEvent. It will be zero if service workers are not
involved.
https://bugzilla.mozilla.org/show_bug.cgi?id=1191943
https://w3c.g
Thanks a lot for working on this, it sounds awesome! Can I ask if there are
any related telemetry probes that will be used later on to evaluate the
results and maybe tune these constants? Do you plan to expose any of these
parameters to web extensions?
Gabor
On Thu, Oct 5, 2017 at 5:27 PM, Andrea
Hi all!
After Bug 1377766 lands, we will increase the amount timeouts
executing in background tabs are throttled, based on an execution
budget. This budget is continuously regenerating, and is decreased
when timeouts execute. If the budget becomes negative, timeouts will
not be allowed to run unti
*# Q3 Codecoverage! update *
/If you //want to hear more about an//y of the//s//e items, please
contact me and I will get you more detailed information/*
*
*## Overview *
We can show the code coverage on new lines added by changeset!
* *Link* - http://firefox-code-coverage.herokuapp.com/
*
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 how much of an outlier your subsessions are...
on Nightl
On 02.10.2017 18:43, Anne van Kesteren wrote:
> On Mon, Oct 2, 2017 at 6:09 PM, Boris Zbarsky wrote:
>> On 10/2/17 12:03 PM, Daniel Veditz wrote:
>>> Fair enough. Could we propose improvements to the APIs that would make
>>> them more usable? For example an object argument to createElement() tha
On 02.10.2017 18:03, Daniel Veditz wrote:
> Fair enough. Could we propose improvements to the APIs that would make
> them more usable? For example an object argument to createElement() that
> contained attribute/value pairs?
>
> var div = document.createElement("div", null, {"id":"foo",
> "cla
14 matches
Mail list logo
