1. 51
  1. 27

    Having menus and toolbars be completely keyboard accessible is huge. Being partially blind (and fine/gross motor impaired), the mouse is an absolute 1000% productivity killer.

    Being able to drive my computing universe from the keyboard as much as possible is critical. This is, FWIW a big reason that I fell in love with the Mac years ago when they actually gave a crap about HID guidelines.

    Linux is getting better and better in this regard, and KDE has always been pretty good.

    1. 1

      Sadly still no support for vertical tabs. :-/

      1. 3

        Every Firefox post feels like groundhog day with this vertical tabs stuff.

        1. 2

          :-)

        2. 3

          I have been using vertical tabs in the latest Firefox for quite a long time now, there was only maybe a week after the release of the breaking version where there was no good solution available. Not sure what else you want?

          1. 1

            I try those extensions from time to time. They are all terrible.

            I rely on vertical tabs to de-clutter my UI and free up some vertical space. All the extensions are a complete failure in this regard:

            • Their horizontal tab bar still takes up space.
            • Their sidebar headers add additional clutter.
            • Their visual metaphor is wrong: the location bar shouldn’t “own” the tab bar, it belongs to a tab.

            Compare my user interface to whatever fresh hell Firefox extensions do these days.

            1. 1

              It’s not ideal, but you can hide the horizontal tab bar and the sidebar headers with userChrome.css. The Firefox team has said they are going to provide an API for extensions hiding and showing the tab bar in the future. If I understand correctly, it’s hung up a bit because of the security implications of letting an extension do this.

              1. 1

                An API for extensions and struggling with security implications sounds like taking the wrong path. Why not add an autohide option, which should be good enough that you’d turn it on and never show tabs if you use an extension?

                While at it, take the time to allow rows of tabs as a built-in feature and not care about APIs.

                But no, none of this will probably ever happen.

                1. 1

                  It’s not ideal, but you can hide the horizontal tab bar and the sidebar headers with userChrome.css.

                  This possibility will go away.

                  Firefox 69 already requires an opt-in in about:config: toolkit.legacyUserProfileCustomizations.stylesheets: true

                  The Firefox team has said they are going to provide an API for extensions hiding and showing the tab bar in the future.

                  They say a lot, but even if they addressed this issue, there are still multiple other deal-breakers, most of which will never be addressed.

            2. 2

              Wasn’t that implemented as an extension in the old XUL days?

              Actually looks like there’s a new one too: https://addons.mozilla.org/en-US/firefox/addon/vertical-tabs-reloaded/

                1. 3

                  The extension is little more than a proof-of-concept, but a good demonstration of all the things that still don’t work (and probably never will) since they broke the old API and killed off their own Tab Center experiment.

                  The state of vertical tabs in Firefox is the equivalent of Go’s “those aren’t angle brackets, they’re characters from the Canadian Aboriginal Syllabics block”.

                  1. 2

                    Yeah they lots a lot of things in the transition to the new API, but given the insecure nature of XUL I can understand why they made that difficult call.

                    I’m still pining for the loss of It’s All Text :)

                    1. 2

                      It comes down to Firefox being obsessed with their 100% fit on their mythological “average user” (that doesn’t exist), not their inability to address this issue.

                      In the end I transitioned to Vivaldi, who – despite the much smaller team – seem to manage to simply ship vertical tabs as a fully supported options out of the box.

                      It kinda sucks, because I’m adding +1 to the already concerning market-share of Chromium-based browsers, but after being a loyal Firefox user for almost 15 years – I’m sick and tired of them trying to be a Chrome look-alike.

                      1. 1

                        At least Vivaldi is open source. That’s pretty important.

                        I’m less concerned about the renderer and more concerned about transparency.

                      2. 2

                        In case you’re not aware of them, It’s All Text has several replacements: GhostText, Textern, Tridactyl and a few others the name of which I can’t remember.

                        1. 1

                          Tridactyl is awfully cool but also awfully invasive in that it turns your Firefox into a totally Vim style keyboard driven experience :)

                          Texterm has platform restrictions, and GhostText looks like it has good potential but you can’t invoke it with a keyboard shortcuts on Macs due to some firefox bug or other :)

                          Thanks though!

                      3. 1

                        I’m curious what you feel is missing from the tree-style-tabs extension? It seems to work fine for me, but mostly all I care about is that it’s vertical, can group tabs, and shows me what container they are in. Every now-and-then it gets a little wonky, but usually just hitting F1 to hide and show it fixes it.

                        1. 2

                          I rely on vertical tabs to de-clutter my UI and free up some vertical space. TST is a complete failure in this regard:

                          • Horizontal tab bar still takes up space.
                          • The sidebar header adds additional clutter.
                          • The visual metaphor is wrong: the location bar shouldn’t “own” the tab bar, it belongs to a tab.

                          Compare my user interface to whatever fresh hell Firefox extensions do these days.

                          1. 1

                            Okay, so it’s non-obvious, but just add this to .mozilla/firefox/[profile.dir]/chrome/userChrome.css:

                            #TabsToolbar { visibility: collapse; }
                            #sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] > #sidebar-header {
                              visibility: collapse;  
                            }
                            

                            And you will have something lovely like my user interface

                            I agree that the location bar location isn’t perfect, but that bothers me less. it’s possible you could drag things around to fix that too, but I haven’t tried.

                            1. 2

                              just add this to .mozilla/firefox/[profile.dir]/chrome/userChrome.css

                              This approach will stop working in the future.

                              Firefox 69 already requires an opt-in in about:config: toolkit.legacyUserProfileCustomizations.stylesheets: true

                              You can probably guess what happens next.

                              1. 1

                                hrmm, that sucks. given the popularity of this approach, i sure hope they have some migration path for users like me. if not I may have to join you in jumping ship.

                                1. 1

                                  btw: from the bugzilla and the announcement it doesn’t sound like they plan on having this actually go away.

                                  You may or may not trust mozilla to not take this away, but I’m not quite jaded enough to switch browsers when they are explicitly saying they won’t remove it all together.

                                  1. 1

                                    The name of the config key contains the three things Mozilla hates most: legacy, users and customization. I don’t think it gets more upfront than that.

                                    I wouldn’t give it a year until the option is gone.

                                2. 1

                                  I played a bit with chromeCSS and things turned out pretty well: https://i.imgur.com/iOgeSdQ.png

                                  Too bad the whole feature has a sell-by-date already. :-(

                    2. 5

                      WebRender is gradually enabled by default on Windows 10 desktops with NVIDIA graphics cards

                      This is very exciting!

                      1. 5

                        This version supports the prefers-color-scheme media query. I’m excited about this because it means people who prefer light and people who prefer dark can both get their way, with a CSS-only solution, and a setting at the browser scope (or possibly even system scope) rather than individual website settings.

                        You can see it in action with the zig documentation

                        1. 4

                          Also has the macOS-specific fix for the Fallout / RIDL / MDS / Zombieload CPU bugs that were disclosed last week. (Other operating systems dealt with this problem differently, so it did not require a patch from us)

                          https://www.mozilla.org/en-US/security/advisories/mfsa2019-13/

                          1. 2

                            Firefox, for several versions now, has put autocomplete pop-up’s on top of the text field I am trying to type in. It obviously blocks the sight of the text, and now in this newest version, also messes up my keyboard focus and mouse scrolling behavior.

                            It is absolutely awful… and I can’t figure out how to fix it :( The tooltips and regular menus broke around version 50 too displaying illegible text, but I was able to at least fix them with css tweaks in the source. Just it amazes me how they are breaking ordinary widgets that should just work, and now brag that their new menu is usable by keyboard (at least the old menu - even on my system - has always worked).

                            1. 1

                              Which OS are you using? I know that some window managers under X either cause or compound that problem.

                              1. 1

                                Yeah, I’m on Linux and using the blackbox window manager, so surely a rare beast. But nevertheless, firefox used to work fine with this setup (and every other program I use does too) so I still blame them.

                                But you know, I actually hadn’t considered hacking the window manager to move those down a little. That might work…

                            2. 2

                              It would be amazing if Firefox can implement writable streams: https://bugzilla.mozilla.org/show_bug.cgi?id=1474543

                              Given our privacy focus, we’d love to recommend them, but currently can’t. This is critical for streaming large amounts of client generated data (in our case locally decrypted)

                              1. 1

                                Could you folks implement them or is that too far outside the scope of your project to make sense?

                                1. 2

                                  If we had the resources I would happily volunteer us, but as it is we already work on Peergos for free in our spare time.

                              2. [Comment removed by author]

                                1. 6

                                  Clearly for you the glass is half empty :) I celebrate accessibility wins when and where the happen. The idea of accessibility being a high priority for every developer is one I enthusiastically embrace, but as a realist (even a partially blind one) I know that when the rubber hits the road this will never happen.

                                  So, yay a small win! I’ll take it and leave you to your vinegar tasting :)