Live data from Hacker News

Firefox 65.0 released

mozilla.org

251–260 of 422 posts

Re: Firefox 65.0 released

#251
Huge props to the Mozilla crew. Firefox has been an awesome browser and I'm thankful for their product.

My only major gripe is video sort of sucks in it, especially when I'm on my laptop.

I'm glad we're starting to see AV1 rolling out in places. Full support can't come soon enough. Last year at NAB everyone was saying it's about 2 years out from solid support. 2020 should be a good year. AV1 looks pretty promising.

Re: Firefox 65.0 released

#252
post #51

I was intrigued by this statement: > A better video streaming experience for Windows users: Firefox now supports the next-generation, royalty-free video compression technology called AV1 Since I don't care about Windows, I was curious as to whether this had already shipped for other platforms or not. At least using Firefox Developer Edition v66, it works fine behind the media.av1.enabled flag on Linux. ---- Also seem…

> I was curious as to whether this had already shipped for other platforms or not. AV1 support is available on all platforms behing the flag; this release just enables it by default on Windows [1]. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1452146

AV1 also uses the brand new media codec sandboxing feature (RDD process). It has platform specific code, hence why only Windows was ready by 65 (but Mac + Linux should be available soon).

Re: Firefox 65.0 released

#253
post #219

Earlier quoted context omitted.

When did you last look at Tridactyl? - :js is there - You can have numbers with :set hintstyle numeric - You can have Vimperator style link filtering with :set hintfiltermode vimperator - There's no map (and probably never will be), but you can bind sequences of keys to "ex-commands", which is probably 99% of what you want, e.g, :bind t open google what time is it The main problem I have with Tridactyl is that it's p…

You're godsent- `:js` is there now and it works! I tried `:set hintstyle numeric` and the command was accepted but it didn't work. Same for `hintfiltermode`. But that they exist means I it's probably me doing something wrong. I couldn't get bind to work the way I wanted- I typed `:` followed by `bind w :tabnext ` but that didn't work. Also, C-i for opening vim on textareas and C-c for cancelling a page load don't wor…

We don't have much validation on `set` - people can use it to make their own settings if they want - so just because it was accepted doesn't mean that it worked in the way you thought it would...

In this case it's because I misremembered the setting. You want `:set hintnames numeric` instead : )

Regarding bind: as I said, it maps sequences of keys to an ex-command. Your attempt is a sequence of keys to a sequence of keys. The correct invocation is `bind w tabnext`.

We left ctrl-c unbound so it could be used for copy, not least because I know it would annoy the hell out of me. You can rebind it with `bind stop`, but because we only have access to pages after they've loaded a bit, it might not quite work as often as you'd like.

Ctrl-I will only work if you have `:native` installed, and, if you're on OSX, an editor I thought to add, which I think might just be MacVim. I'd hope it would give you errors if any of the above was untrue...

We definitely aren't at feature parity with Vimperator. Some stuff Mozilla just won't let us do (e.g, emenu), other stuff we can do but haven't got around to it yet (accepting keyboard input on privileged pages - we have preliminary approval for extending WebExtensions).

I'm glad I could help. There's `:tutor` which is fairly short and probably the most user-friendly way of digesting general information, and there's `:help` if you fancy a very dry novella; there's also somewhat hidden help pages for settings and commands for use in insert/ex mode, the latter of which I can't remember how to access. I think there's a link hidden on the main help page.

Re: Firefox 65.0 released

#254
post #58

Earlier quoted context omitted.

Firefox is being sabotaged from the executive level, I'm 100 % sure of this. Tech-wise, solid. Administration, a complete disaster.

Probably. It's pretty sad when you see something great stuck in a local minima because of "thinking heads" that know better.

Exactly. And they still don't advertise a lot of the Firefox features outside of release notes. I mean REALLY advertise. Google used to have regular commercials with celebrities to advertise Chrome, and people are still somehow baffled that they're number one now? FOSS devs build some good software, but we're terrible at marketing.

Re: Firefox 65.0 released

#255
Downloaded Firefox 65 (Windows) and quickly loaded a web page... and still no pinch zoom. :-(

I hope macOS & Windows Firefox will get pinch zoom soon, so that I can finally switch from Chrome.

Firefox seems to have good performance and user-centric features & functionality.

Re: Firefox 65.0 released

#257
post #93

Earlier quoted context omitted.

You can disable the ads in the preferences. The telemetry can be mostly disabled there too, more if you use about:config. Pocket, which I assume is the service you mention, can also be disabled in about:config. You can find more here: https://www.privacy-handbuch.de/handbuch_21u.htm This user.js will disable most of the telemetry and other things: https://www.privacy-handbuch.de/download/minimal/user.js So yes, you c…

But it isn't by default, that is the issue

If telemetry was off by default, Mozilla would be blind to what the users are doing, to common sources of crashes and to what features are not being used.

Mozilla needs that information to be able to make a decision on where to focus.

Same for ads, default off ads defeats the entire purpose.

Mozilla is a privacy-aware and even -focused corporation and I will assume that the defaults of the browser are good for the common end user. Everything else may be configured.

Re: Firefox 65.0 released

#258
post #5

>Firefox will now warn you when closing a window (regardless of whether you have automatic session restore enabled for restart). To whoever is responsible for pushing this change through: Thank you.

Note that it still won't warn you if you have the "Warn you when closing multiple tabs" options unchecked. Source: https://bugzilla.mozilla.org/show_bug.cgi?id=502908#c68 > We don't intend to add a third, separate pref/warning for people who do want to have a quit warning, don't turn on session restore, and don't want warnings when closing windows / multiple tabs (ie making browser.tabs.warnOnClose = false + no autom…

FWIW I don't get any warning when closing multiple tabs (through tree style tabs), have session restore turned on, and do get a warning when closing the window.

Re: Firefox 65.0 released

#259

I have turned on Webrender in FF66a (nightly) and it’s fantastic; it sped up a site I quickly threw together for a friend no end [1] and almost everything with lots of graphical painting is buttery smooth. Even though they are only starting in nightly to make it the default on Nvidia hardware it seems to work without incident so far on this 2016 AMD Radeon’d MacBook Pro. [1] https://uparchitects.co.uk/ [2] https://di…

Well the limit in nightly to nvidia on windows is less about saying “we think WebRender only works/is stable on nvidia on windows” than it is about saying “we want more people to try it and possibly send big reports but we don’t want to risk breaking the entire nightly population or have them all sending in big reports, so we will start with a small subpopulation where we think bugs will be due to WebRender rather th…

Ah fantastic, definitely good to stagger the releases. I do understand the driver/stability situation being much more fragmented on Windows, just nice to be able to confirm how big the improvements are to Firefox that are still to come; the fastest browser by a long way IMO!

Re: Firefox 65.0 released

#260
post #17

Earlier quoted context omitted.

Chrome's "hold cmd-Q to quit" popup is just about perfect in that regard.

I really wish this was standard across all apps on macOS. It's beautiful UX, and easily discoverable.

It's not accessible. Applications that are meant to be used by the general public should avoid making assumptions about how the user presses keys. Specifically some users with motor impairment may find this kind of "long-press UX" to be troublesome.
Post reply on HN