Firefox 71
mozilla.org
mozilla.org
For example, I'm running Nightly, and the Dev Tools>What's New tab says the "Debug Variables with Watchpoints" (break when a property is read/written) feature is in Developer Edition (and presumably not in Nightly or the Release channel).
Finally! This was the main reason to develop on Chrome instead of FF for me. The rest is almost comparable with Chrome DevTools for everyday web development.
The fact that the tabs don't shrink, but instead slide out of view is infuriating. Something like this affects users constantly.
I'd love to read any study on the usability of the Chrome approach if anyone happens to know of one. Maybe something on SIGCHI?
In that case, I think Firefox violates this. Your tabs are just gone when you could have sworn they were there a second ago...
In broad strokes, the time to accurately complete a task is proportional to the distance to an item and inversely proportional to the size of the item. So, having to scroll tabs increases the distance -- potentially a lot. But, constantly shrinking tabs reduces the target size. I think you'd have to do an amortized analysis on this one because upon a the creation of a new tab the Firefox model only makes that new tab harder to get to, while the Chrome model shrinks all tabs, making each harder to click.
But, I could buy that there's some threshold here where Chrome maintains a tab size that still doesn't appreciably increase error rate while improving distance by eliminating the tab scroll. I'd expect that minimal tab width to be much larger than Chrome's true minimum tab width. But, I'd be shocked if Google didn't run usability studies on this. I just haven't come across anything on my own.
General position is particularly helpful because, from left to right, it roughly represents "time opened", earliest to latest.
Firefox doesn't help me find the right tab just by including an 8 character width along with the favicon. Might as well just get rid of those 8 characters.
Safari used to have fixed size tabs as well back in the days of yore, I still miss those.
Setting the "browser.tabs.tabMinWidth" preference to 0 in Firefox will let the tabs shrink down fairly small (to just the favicon and maybe one letter of the title). If you want the tabs to shrink even more than that, I'd like to understand why, other than "it's what I'm used to". Which, to be clear, is a perfectly valid reason to want something!
But in general, it's very upsetting that Firefox doesn't actively support editing these user setting fields.
My experience was that if you changed even a single boolean value, the answer to every support question was "reset to default settings and see if it's still broken". Just awful.
If a killer, life-changing extension exists in Firefox which is not available on Chrome, this is that extension.
.tabbrowser-tab {
min-width: initial !important;
}
.tab-content {
overflow: hidden !important;
}
I can see how I missed it, they made a clickable link/button the same color and style as the other non-clickable text: https://i.imgur.com/gqlCVRo.png
browser.tabs.loadBookmarksInTabs;true
toolkit.cosmeticAnimations.enabled;falseWhat does "native" mean in this context? Uses accelerated CPU instructions? Uses the codecs of the system instead of something Firefox has built-in?
[0] https://developer.mozilla.org/en-US/docs/Web/Media/Formats/A...
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1582271
[2] https://github.com/mozilla/gecko-dev/blob/master/media/ffvpx...
https://blog.mozilla.org/blog/2019/12/03/news-from-firefox-o...
And I tend to load FF, use it for a few minutes, and then quit it. That's because FF has a habit of going nuts somehow, and gulping energy on my OSX systems. I've no idea what causes the problem, and I don't really care, because Safari tends to be faster -- sometimes a lot faster.