1. 39
  1. 19

    “Firefox now prevents websites from automatically playing sound.”

    Now, that’s Mozilla listening to its users. :)

    1. 11

      More like…not listening…to autoplaying sound!

      …it was funnier in my head

      1. 3

        It’s also funny outside of your head, don’t worry :)

        It sure is a great addition to Firefox.

      2. 4

        this isn’t really a new feature–Firefox has actually prevented websites from playing sound on my machine for years.

        they removed support for ALSA and only play thru PulseAudio, which frequently simply refuses to play any audio for no reason.

        1. 1

          Hey! Pulseaudio is fine as long as connected audio outputs never change. Or have ever changed. Most of the time.

          1. 1

            Most of the times, execute pulseaudio -k will bring the sound back.

            1. 1

              What I found more reliable was to uninstall pulseaudio and use alsa, which works perfectly, every time, without flaw, in every program except firefox.

        2. 3

          Easier, passwordless security: Added support for Windows Hello on Windows 10, allowing you to use your face, fingerprint, or external security keys for website authentication

          Oh this is cool! I wonder if something like this could be added for Linux/BSD because of fprint + PAM. The U2F stuff has been there for a while.

          1. 3

            Now that Firefox 66 has been released, Nightly has been bumped to 68, but it seems to have introduced two bugs that annoy me:

            1. 3

              Ugh! They seem fixable fortunately. Thanks for using nightly!

              1. 8

                In the few hours since I made that comment, both tickets have been triaged, confirmed, and the commit that caused each regression isolated. I’m quite impressed, I hope the fixes are equally fast!

                1. 2

                  Well, that was the easiest part :-) do you have bug numbers handy for everyone reading along?

                  1. 2

                    I, uh, linked them in my original post. :)

                    Both bugs now have patches attached!

              2. 1

                Can you comment on how well TST works for you? I found that it wasn’t really worth using anymore after the move to web extensions.

                1. 4

                  The original, pre-WebExtension version of TST physically moved the tab-strip from the top to the left, and that’s just not possible with WebExtensions. Some people have gone to extraordinary lengths to recreate the original TST appearance, and while I agree that would be nice I haven’t bothered - as long as I have a scrollable, collapsible list of tabs with a big ol’ new-tab button in the lower-left corner, I’m quite happy.

                  Earlier versions of TST were a bit weird with the tab context menu, because sidebar extensions can’t draw anything outside the sidebar, so the context menu had to be faked up in HTML, which meant it didn’t include any context menu items from other extensions. However, TST’s author collaborated with Mozilla to add a “tab context menu” API, so an extension can ask Firefox to pop up the real context menu for any particular tab, so now it all works as expected.

                  The one wart I can think of with the current implementation is that if you drag a tab out of the sidebar, you might drag it onto the bookmarks bar to file it as a bookmark, or you might be dragging it out to create a new window, and WebExtensions can’t detect drop targets like that. Instead, there’s a little menu that appears when you hover over the left-hand end of the tab that presents the two options. It’s nice that it’s possible, but it’s definitely a bit clunky and I can imagine it would be annoying if you did either of those things on a regular basis. However, I don’t, so I don’t mind.

                  1. 2

                    Interesting to hear!

                    I really tried to accept the brokenness of vertical tabs in Firefox, but considering the sorry state I don’t feel to bad about switching to another browser.

                    For me to switch back to Firefox, would require Chrome to add vertical tabs.

                    Chrome doing something seems to be the only way any non-beginner problem gets recognized by Mozilla these days.

                  2. 1

                    TST works great for me. I use it every day and depend on it as a key part of my browsing experience. I find the WebExtension build quite good. The add-on author has even added quite a lot of features beyond what it had before the rewrite to WebExtensions.

                    I basically can’t use other browsers for an extended period at this point because I am quite dependent on TST.

                    1. 1

                      Thanks for the note. Vertical tabs are also a key part of my browsing experience, but since web extensions were introduced Firefox just didn’t cut it anymore for at least two reasons:

                      • That you can’t get rid of neither the horizontal tab nor the sidebar header feels like a cruel joke to me.

                      • The visual hierarchy (nav bar -> tab bar) is just wrong, it should be the other way around. I’m too tired to fight this fight again (remember how long it took to get the tab bar placed above the nav bar, instead of under it?).

                      So it’s interesting to hear that TST is still useful for some set of the original users of TST/Firefox.

                      1. 1

                        That you can’t get rid of neither the horizontal tab nor the sidebar header

                        You can in fact get rid of both, though it’s with a UI style override and thus somewhat inelegant. My chrome/userChrome.css file has the following to hide the default tabbar and the sidebar header for TST:

                        /* Hide top tab bar */
                        #main-window[tabsintitlebar="true"]:not([extradragspace="true"]) #TabsToolbar {
                          opacity: 0;
                          pointer-events: none;
                        }
                        #main-window:not([tabsintitlebar="true"]) #TabsToolbar {
                          visibility: collapse !important;
                        }
                        /* Hide sidebar header */
                        #sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] #sidebar-header {
                          display: none;
                        }
                        
                        1. 1

                          Yep, I’m using some CSS hacks in Vivaldi on top of its existing native support for vertical tabs, but I simply have not enough trust left in Mozilla to believe they aren’t itching to lock down the user chrome in the future.

                          Nevertheless, I’ll give your CSS a go and report back! Thanks!

                          Edit: I just did the comparison!

                          How it needs to look (Vivaldi).

                          How it looks (Firefox).

                          I don’t think Firefox will ever be able to cross this gap, not even taking into account the lack of tab-previews, the lack of built-in mouse gestures, and the many other things that put Vivaldi ahead UX-wise for anyone who is using a browser for more than 5 minutes a day.

                          1. 2

                            anyone who is using a browser for more than 5 minutes a day

                            I think it would help to clarify that all of these features are very opinionated, so I don’t think it’s helpful to generalize and assume “anyone” or even “most people” using a browser want these things… (IIRC a high number of browsing sessions never have more than a few tabs open, for example.)

                            For myself, TST / a tree of tabs is important, but at the same time I don’t need mouse gestures or these other things you mention. It sounds like we are both quite set in our own way of using a browser, but I don’t think we should assume anyone else actually wants or should want the same. That’s the point of customizing: to find what works best for you.

                            1. 1

                              I think the core problem is that Firefox has become increasingly hostile to customization over the years – it’s either Firefox devs’ sacred idea of how the average user has to use their browser, or the highway.

                              Nothing has changed much on my side in the last 15 years I used Firefox, except that Firefox has decided I’m not part of their target demographic anymore. That’s sad, but I think it’s best for me to move on.

                        2. 1

                          I am not bothered by the sidebar header or horizontal tab bar still being present. As mentioned by @whbboyd, you can customize userChrome.css if they bother you, but I don’t see a need to do so for my own use.

                          The precise feature set and customization options of TST are more important to me, so as long as I can view the tree of tabs on the side with TST features, I find that good enough.

                  3. 1

                    I know it is confusing, but we actually have browsers tag which this should use instead.