Firefox 86.0
mozilla.org
mozilla.org
Ctrl-1 to Ctrl-8 accesses the first eight tabs directly, Ctrl-9 jumps to the last tab. Enjoy!
1. https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&comp...
In the case of the new print preview/workflow, however, I expect it will provide virtually everyone with a better workflow once we've finished polishing any rough edges. The feedback on places like Reddit indicates that it's already a very clear net win for most users, and I think we can address most of the complaints on support.mozilla.org etc. The eventual removal of the `print.tab_modal.enabled` preference and the old code will simply be because having two print preview implementations adds code complexity and is a maintenance burden.
I understand that the needs of any one user, such as me, with a particular idiosyncratic set of needs and preferences are at odds with those of the body of users as a whole, who need an appropriate balance between customiseability and useability, together with, of course, deliverability—it's no good having a product custom-tailored to fit every possible combination of needs if the developers collapse under the maintenance weight.
I didn't really mean what I said as anything other than a cri de cœur: it sometimes seems that Firefox rode to its current position on the wave of the love and passion of power users, a group of which I am on the periphery, but now cares more about its numerically larger but less devoted casual user base. This is probably the right decision, but it's still frustrating as one of those long-time users (from back in the Phoenix days!).
I really dislike this philosophy of replacing the system functionality. Particularly on Mac where the system functionality is quite good. (On Windows and Linux, I admittedly don't care as much, because nothing is ever consistent anyway...)
This makes me happy.
The Browser Toolbox is the normal DOM inspector, just extended to the whole user interface. If you open the print preview, then open the Browser Toolbox, you can inspect the preview and edit styles just like any other document.
Also, @media print {} works fine, I just tested it. But I'm not sure how that relates to the original question.
I seem to remember the controls for page fit being a little better with the old print preview, but my real complaint is with websites that don't scale well to print rather than Firefox's method of printing them.
Ctrl+Shift+N works in Chrome but in Firefox its Ctrl+Shift+P.
Is Adderall the new Aspirin? Or is there some WFH use here that I'm missing.
https://w3c.github.io/picture-in-picture/
https://github.com/w3c/picture-in-picture/blob/master/explai...
https://developers.google.com/web/updates/2018/10/watch-vide...
https://bugzilla.mozilla.org/show_bug.cgi?id=1463402
https://www.chromestatus.com/feature/5729206566649856
Looks to me like it is a standard that web devs requested (e.g. so you can scroll down YouTube or whatever and the video will keep playing in the corner), which Firefox chose to also make an end-user UI for.
Me personally, will probably stick to one video playing in the background. It's more for ambient noise. On days when there are 4 nba games going on simutaneously, I'm far too busy fiddling with my spreadsheet/nba feed to be actually watching the game.
If there’s something I’m watching but not giving my full attention to - say an event hasn’t started yet or someone will be landing a rover on Mars in an hour - this means that I can either have a big chunk of my screen wasted or I can use PiP and have just the thing I care about using a quarter of the space but showing considerably more of the actual content.
Plus, it uses well-tested standard controls so I don’t have to play games figuring out whose <script> kiddies don’t think about keyboard shortcuts or test their event handlers.
And it's just more convenient than trying to maximize the space of another browser window and making it stay put above other stuff. No extra chrome, no wasted inline space on the page. I can just take a Blender tutorial for instance and move directly above my Blender window and it obscures as little as possible.
1. unusably small 2. full screen. Which often means unusably large (27" screen), especially for less-than-HD videos
At least youtube added at some time the cinema mode which allowed the video to occupy the whole window width, that is what I use most of the time. Still, PIP also has the advantage of removing the window decorations, so saving space. Also, they are floating on top of all other windows, which helps, but also occasionally can be annoying.
PiP seems to be a cleaner solution.
The problem is browsers have two layers of decoration: the WM layer (which tiling window managers tend to remove), and the internal layer - the tab bar, address bar, option buttons, borders, etc.
As far as I know, there isn't a way to remove all that without going full screen.
I can have 4 different sources on at the same time (music in the background - quiet, one of the news channels a bit louder if I'm waiting for something to happen, a corporate all-hands zoom call I'm half listening to on the main computer, and maybe a short video or meme, it's usually 2 or 3 though.
I don't use pip much as the one site I'd use it on (twitter) works hard to stop the video playing as you scroll down anyway.
- I often would like to watch one team member update Trello or Mural, at the same time as another updates Github, while I update a contract. I'd move those streams to my 4k monitor, to keep them readable, while I work on my primary.
- If I'm running a demo to a client, I'd like to have one stream sharing the demo platform, while another shares video of my haggard face, and a third shows my presentation. I don't want to share my whole desktop, to avoid sharing slack or SMS notifications.
OBS can probably do #2. Nothing does #1.
The only thing I miss are subtitles in Picture-in-Picture mode.
OS-provided window border and titlebar
Standard menubar with keyboard hints, always displayed
Five buttons: Back, forward, reload, stop, home
Address bar and separate search field
Status bar which shows me link URL when I hover a link
[1] https://www.webdesignmuseum.org/web-design-history/mozilla-f...
Personally, these days I use a keyboard-driven browser without any of that stuff, just the frame, vertical tabs on the right, and a status bar. But for people in my friends and family circle, I think that interface would be infinitely more functional and productive than anything else I've seen.
Tick "Title Bar"
Drag & Drop the "search" widget aside your URL bar
Drag & Drop the Five buttons you mention where you want
You're welcome.
(for the status bar URL link preview on hover it's already the case by default)
I would also note that the address bar and search box got merged for a good reason, because their functionalities steadily converged over time as the address bar became more powerful and useful. You can still have them split if you really want, but it is unlikely to actually benefit most people.
Why. Just why.
My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, so instead of fixing the migrations, they decided that this user-hostile anti-feature was good enough.
I think this is actually a good feature, one of the few introductions which I think if worthwhile, even if the implementation is a bit lacking.
You have to balance the user being able to see the message with not annoying them, and it's not difficult to achieve.
Configuration bloat is a real problem in most applications which allow third-party extensions, and I've seen some stunning examples of extensions bloat on some people's computers, Chrome users included. On the other hand, when I question it, they tell me, "I use all those!"
This article I came across here on HN really enlightened me: https://www.asktog.com/columns/000maxscrns.html
Having a button somewhere where the user can go and reset those things is ok. But keeping pestering them until they click on the button is really not.
It sounds like something which started out as a good idea and was then steered into user abuse territory.
The status bar is not persistent.
Also, for whatever reason, the URLs displayed in the status bar are cut off with an ellipsis, even when they would fit inside the window.
The menu bar -- File, Edit, View, etc. -- is still not displayed. And when it is displayed, the keyboard accelerators are not. I do realize this is in part the window manager and OS's accomplishments.
By the way, most of the actions you described are not even possible without using the mouse. Firefox, and most desktop applications, used to be 100% accessible without using the mouse. (Mac has always been an exception, but it was covered 100% on Windows and close to complete on GNU.)
I can't imagine it being that difficult to implement as a feature. If the setting is on, you would skip interpreting any <style> tags and style= attributes.
Past versions of many browsers support selecting between multiple stylesheets specified by the page, as well as provide your own stylesheet to use in place or in addition to the page's stylesheet.
(This was one of the main, amazing fucking benefits of CSS, to separate presentation from content, so that users who were hindered by the page's styles could turn it off and still be able to view the content.
And all of it works great if you do it right, because the styles cascade, and, I apologize for repeating myself, the content layer is separate from the presentation layer.
At some point all these features went away, 'cause fuck accessibility, I guess.
Meanwhile, CSS became Turing complete, so security-wise it's like having a second JavaScript which cannot be turned off.
Great progress all around. /s
When people ask me why I spend time on ensuring that I support older browsers in my projects, this is one of the reasons. Sometimes I just want to use a decent fucking browser that's not been lobotomized, and at least I can do it on my own sites.
(I usually apt install before testing and apt remove after, because otherwise it often becomes the system default.)
On the other hand, if this is the kind of approach to UI you like personally, I think the Vivaldi browser would be up your alley (sadly not open-source though).
https://news.ycombinator.com/item?id=26276871
Vivaldi is OK, but it's proprietary AFAIK?
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...
Note also that release schedule is now 4 weeks instead of 6 weeks. Hence each release might feel "smaller".
There are actually a lot of nice improvements being discussed in the CSS level 4 specs, but some of the issues are last tagged as updated in 2012...
But basically we just need a consistent value interface (two-way data binding), and a more finely-grained validation/state lifecycle where we can plug in our own custom validation functions.
Colleagues and I always joke that every web developer gets the idea to write a form library at some point, and suffering through trying to implement it is the only way to dissuade them of the idea. Now the joke is on me as I’ve come full circle back to writing one.
I’ve spent so much time on it now I’ve been considering reaching out to help contribute to the spec. But I have no idea how receptive the working group is. This may just become my eternal project, there’s always more edge cases to find.
https://blogs.windows.com/msedgedev/2019/10/15/form-controls...
This Firefox changelogs are awesome to know big improvements and new features on a surface level.
For Chrome I didn't find a proper way to follow the releases even if it has some RSS feeds, I follow the RSS feed of Chrome Releases blog [1] with a tag filter [2] but can't exclude the several point releases, and also the changelogs are not very informative [3]. And the Chrome blog [4] I get some feature announcements but is a mix bag.
[1] https://chromereleases.googleblog.com
[2] http://googlechromereleases.blogspot.com/feeds/posts/default...
[3] https://chromereleases.googleblog.com/2021/01/stable-channel...
And here's my lua script that uses notify-send to notify me of new releases: https://gist.github.com/folknor/32f703b270c6ad72bc12d98feb2f... I modified it slightly before posting it here, but it's mostly useless unless you're me :-D Because when I write shell scripts (which I always do in lua), I always use my fork of luash (from my github), and I don't imagine anyone else has it. It's easy enough to rewrite the script to not require it, though. Also, the other obscure dependency it uses is lua2xml, which is notoriously unreliable, but I still use it in all my shell scripts that interact with XML.
It's hidden behind a right click menu. So it's a muscle memory friendly change. I don't remember the url bar change to be too disorienting either.
It's not really. Now when you right click (long press) to open a link on a new tab it opens it in the same tab group as your tab. If you then use the button at the top to switch tabs (how it worked before), you are now switching tab groups. To switch tabs in your tab group, you have to do it at the bottom.
This should be possible on Firefox too: https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugg...
It's slow as molasses and loses UI events. I had auto-update turned off so I didn't use the new Firefox for Android until recently, and now I sincerely regret I updated it.
They also did something silly with trying to match your tap to closest link even if your tap falls squarely outside of the link's activation area. It's super annoying on sites with small text, like HN.
On the flip side, the UI being garbage made me stop browsing HN on my phone, so overall, perhaps that's an improvement in terms of my productivity.
Same with Firefox on Desktop, for that matter.
I'm on Waterfox Classic on desktop, but that's probably not gonna last forever either. And when that eventually drops support, I'll just stay on the last version until some browser vendor brings multi row tabs back. On mobile, I visit maybe five websites, and the three most common ones don't have ads, so I'm happy with my pinned old Firefox Beta version. And no matter what happens, I'm not upgrading to current Firefox on Android - well, unless the thing that happens is they take that abomination of a UI back behind the shed and put it out of its misery...
The way I look at it, it's unfortunate that the one single browser actually worth using sadly no longer gets security updates. That sucks for me, but I'm also not gonna stop using the browser.
Apparently this has been available to users in the US since v81, and will be available to other locales in the future. Out of curiosity, how are these features gated geographically?
I am a happy firefox user and the print preview is one of the very few things that made me open chrome backup.
https://bugzilla.mozilla.org/show_bug.cgi?id=1041377
That key binding was added for interface compatibility with Internet Explorer, which is less important these days. If you'd like to disable it now, go to about:config and set browser.backspace_action = 2.
http://kb.mozillazine.org/Browser.backspace_action
Apparently, you can use value 1 to use backspace to scroll a page if you like!
In a redirect, the third party site is used as a friest party request, and should not be limited by this.
See same site cookies and referrer policy to limit how much information is leaked to a third party with redirects.
I've always tried to set up delivery of all static assets w/out cookies so that I do not incur the performance overhead. Not that it makes a huge difference except on very large sites. But last time I checked, performance & speed-test tools even remove points if this isn't done. Seems this is a feature not a bug or am I missing something?
I knew it had added that feature but I didn't actually try it until just now. And oh my god you can FOLD the group... tab management just got a lot better for me!
Improved from roughly 760 to 700ms on my 5800X.
Still ways to go to reach Chrome at 560ms
JPEG XL and/or WebP2 are looking to be great but there is not reason to wait for perfect to come along before adding another format to the browsers - it's not like they are running out of room for more image decoders :).
When I watch Twitch or take a Zoom call in Safari the fans may come on, but it never gets anywhere near as hot. Honestly think it's dangerous to the battery life.
According to Apple's Energy Usage stat, Firefox uses "57" where Safari uses "1.7" for the same Zoom call.
Given how much is done on streaming video calls now, love it if Firefox made this a priority.
worked perfectly before, again a case of 'if it works -----'
the `print.tab_modal.enabled` preference to `false` fix described below helped
about:config
browser.newtabpage.activity-stream.showSponsored
browser.newtabpage.activity-stream.showSponsoredTopSites
there is also:
services.sync.prefs.sync.browser.newtabpage.activity-stream.showSponsored
services.sync.prefs.sync.browser.newtabpage.activity-stream.showSponsoredTopSites
This has happened before with the browser toolbar having an about:config option to disable enlarging behavior, now you have to do some hacky CSS thing.
> We intend to add a keyboard shortcut for this[1]. In the meantime you can revert to the old printing interface by setting the `print.tab_modal.enabled` preference to `false` via the page `about:config`. In a few releases time, after we've finished integrating user feedback and polishing rough edges, we intend to remove that preference though.
1. Click the "Customize your New Tab page" gear icon on the New Tab page.
2. Uncheck the "Sponsored Top Sites" and "Sponsored Stories" checkboxes.
Say what you want about Safari being outdated etc. but at least they’re not going to pull shit like this.
I'll detail my opinion on the path forward for Mozilla and Firefox in particular.
Surprisingly it's been Firefox on iOS that's the biggest pull to keep me on FF overall. I think that's the real way forward for them. There's just too many Google nags to switch to Chrome on the desktop. This is limited on mobile, and putting all resources into mobile features is paramount. Then desktop version usage increases due to sync features.
I'm a Windows and iOS user, and on the desktop, zippiness is feature #1. I think they should move to Chromium, as unpopular as that is. It'll save on maintenance and an un-Googled Chromium like Edge is a very good thing. Leave FF exactly as it is, all features intact with Chromium underpinnings, borrow a few features from Vivaldi (horizontal tab support), and you easily have the best browser on the market.
On iOS, it needs support for the URL bar to move to the bottom as on Android. It needs uBlock Origin integrated by default, to borrow from iOS Edge having adblock. Improving dark mode is key. I just can't get it to work properly with DuckDuckGo's homepage. Images are sometimes reversed. I've had to turn it off to get pages to display a their native black background. I'd like to see it work out of the box with Facebook's messenger feature, it tries to redirect to the app, while in Safari this can be set to open in desktop mode and just works. Otherwise, general stability improvements and performance. It used to be very unstable, but its come a long way now. It's my favorite mobile browser.
Would those changes be enough? I'm not sure, but I do know iOS and Android browser support is the only possible way forward other than services like their VPN.
I'm the type of user though that doesn't mind the ads in the URL bar, pretty small ask on Mozilla's part. I also leave telemetry enabled because I want my usage scenario to be in Mozilla's data. As you can guess, I'm not the typical user that thinks Blink vs Gecko is somehow a mighty crusade to save the web. Even if it were where the real battle is, Mozilla is not the entity that's properly armed to take up that fight. Apple or Microsoft would be.
I have other ideas on how to move Mozilla forward and make it a very big player in the tech space. The biggest problem confronting Mozilla today is probably Mozilla. If I had to guess. Trying to convey these ideas to leadership and get a path forward set in the bureaucracy is probably pretty tough.
I’m sorry, but I only have 8 hours a day, and I’m not going to let my productivity flow get ruined.
It does sadden me that some sites are starting to refuse to work with Firefox these days... But I won't give up.
That said, Google has a long history of making their products glitchy on Firefox, so not sure it's all Firefox's fault.
https://www.zdnet.com/article/former-mozilla-exec-google-has...