Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 64 Released

hacks.mozilla.org

Post reply on HN
Print view View original

271–280 of 527 posts

Re: Firefox 64 Released

#271

Post by gnicholas »

gnicholas wrote: post #80
rerx wrote: post #2

Does it come with Mac performance improvements?

I have used Firefox since the early 2000s, and it has been frustrating to see performance get worse even as my hardware gets better. I realize that this is mainly the fault of bloated websites, but I can also see that Chrome and Safari are faster than Firefox. I recently switched to Brave Developer Edition [1], which now supports Chrome extensions (which I need for work/pleasure). It runs circles around Firefox and C…

I'm curious about the downvotes — anyone care to enlighten?

Re: Firefox 64 Released

#272

Post by idoubtit »

sinistersnare wrote: post #102
idoubtit wrote: post #85

The new API browser.menus.overrideContext is announced with documentation links pointing to blogs, including a personal blog page with unrelated Japanese texts and anime pictures. The official documentation (MDN) has no reference to the new features. Even the API features from FF63 (august 2018) are only have a draft of documentation (e.g. Menus.getTargetElement). Documentation is important, even more for an API. I t…

Yeah, the feature is not introduced that well. It is mostly a good feature for the extension that they are talking about, TreeStyleTab[1], which explains the feature. Piro's blogpost is actually awesome. It describes the history of the feature, and how it is used today in his extension. However, they could stand do the documentation themselves, or at least setting up the context of the blog-post a little more. I am n…

In this case, I don't care much if the blog is pretty or not and who wrote it, even if Tree Style Tabs is my main reason for using Firefox. The problem is that Firefox is relying on an external source as the main explanation of their new API. Will the URL still be right in a few months? They have no control over it.

MDN is one of the best achievements of Mozilla, so I worry when I see it is not updated with their own technologies.

Re: Firefox 64 Released

#273

Post by pbhjpbhj »

jjuhl wrote: post #133
shmerl wrote: post #89

Earlier quoted context omitted.

Why would beta build not find shader cache?

Beta == unfinished, may have bugs.

No, "beta" means "finished, but may have non-show-stopper bugs".

If it's not finished it's alpha.

Beta is pretty much just used as "buyer beware" nowadays, like a disclaimer "we take no responsibility for our bugs".

Re: Firefox 64 Released

#274

Post by camjohnson26 »

andersha wrote: post #176
kentosi wrote: post #172

Good work guys. For those using Firefox, I have one question. Is there any way to replicate Chrome's tab-to-search feature? It's literally the ONLY reason I'm still on Chrome. Let me explain by showing how I would search for "apples" in youtube across both browsers. Firefox: 1 - Ctrl+L (go to location bar) 2 - Type "you", press "down" to select youtube from history. 3 - Wait for site to load...... 4 - Click on search…

Hi, I am using firefox with duckduckgo. Firefox + DDG = Ctrl+L - Type "!yt apples", press enter https://duckduckgo.com/bang

!hn for hacker news, !gi for google images and !wt for wiktionary.

Re: Firefox 64 Released

#275

Post by kissickas »

amarsahinovic wrote: post #261

I really wish they would implement tab stacking, that is the feature that I really miss from the old Opera, here is a video of how it looks in case you don't know: https://www.youtube.com/watch?v=VWpJvg8icmM I've tried to find an extension for FF that does this, but so far I was unable to find one.

Have you tried out TreeStyle Tabs? It has all of the stacking features I saw in that video, but doesn't have the preview features (maybe you can use it alongside another extension that provides that).

https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...

Re: Firefox 64 Released

#276

Post by daleharvey »

Misdicorl wrote: post #262
daleharvey wrote: post #226

Earlier quoted context omitted.

pref("media.autoplay.default", 2); // 0=Allowed, 1=Blocked, 2=Prompt https://dxr.mozilla.org/mozilla-central/source/browser/app/p...

Curious: How is a prompt ever better than simply expecting the user to click the play button?

We thought it could let users enable it for sites where they wanted it as a feature (netflix, youtube, games etc)

Turned out to be wrong, thats why we will be shipping blocked by default

Re: Firefox 64 Released

#277

Post by fao_ »

nine_k wrote: post #127
fao_ wrote: post #33

Earlier quoted context omitted.

> but this addon promises to restore it Mozilla did the same with tab groups, then the addon was abandoned. The replacement that is compatible with the new form of extension isn't able to unload the tabs, just hide them, which undoes most of the performance benefits. [abraham simpson voice] It'll happen to you too! [/abraham simpson voice] /jk

FWIW, Tree Style Tab solved tab groups (and more) for me. I wish tab handling had a first-class API in Firefox, so that different tab managers could interact with the default tab menu, etc.

> FWIW, Tree Style Tab solved tab groups (and more) for me.

Yes, but I don't really want tree-styled tabs, I want tab groups :P The interface is vastly different.

Re: Firefox 64 Released

#278

Post by acqq »

zeotroph wrote: post #204
acqq wrote: post #147

Earlier quoted context omitted.

> This is completely unnecessary It is completely necessary for me to have “move one page up on click.”

But, that is what PgUp/PgDown are for on the keyboard, no? When you are navigating in these discrete steps why use the mouse, which is excellent for continuous input. If I click on something, I want to go THERE, not in the direction of it. "But we have always done it in this (imo illogical) way" is just being stubborn.

> that is what PgUp/PgDown are for on the keyboard, no?

Definitely no: If I have a hand on the mouse I surely don't want to lift it and hunt for the PgUp or PgDown just to move one page up or down. And no, I don't want to go "there" if it's actually "somewhere" in the middle of whatever, if I just want to see the previous or the next page. Going "there" is much less frequent operation than moving to the next or the previous page.

Re: Firefox 64 Released

#279

Post by daleharvey »

drbawb wrote: post #265
daleharvey wrote: post #219

Earlier quoted context omitted.

I introduced the change to 0,1,2. Not sure what happened when we first introduced autoplay but the change to 0,1,2 was so we could let users switch between enabled, disabled and ask the user. Original plan was to ask the user by default. We did some user testing with this change and it looks like we will be changing it to block by default based on feedback Not sure what this has to do with any companies ad revenue, o…

Block by default, and not ask by default? That seems unfortunate to me, and will definitely break one of my services for Firefox users. I have a site which coordinates watching videos amongst a party of people. To the browser heuristics it looks like "autoplay" (the host starts the video manually, and some scripting on the page kicks it off for everyone else and works w/ the backend to maintain something resembling s…

It sucks when you want to use feature that arent available however users wishes always trump site authors, we tested ask by default and it turned out more users wanted them blocked

"Click here to play video" is also clear and easy to understand, not sure why you would think your users could not handle that.

In future https://developer.mozilla.org/en-US/docs/Web/API/Permissions... may help

Re: Firefox 64 Released

#280

Post by [deleted] »

Misdicorl wrote: post #262
daleharvey wrote: post #226

Earlier quoted context omitted.

pref("media.autoplay.default", 2); // 0=Allowed, 1=Blocked, 2=Prompt https://dxr.mozilla.org/mozilla-central/source/browser/app/p...

Curious: How is a prompt ever better than simply expecting the user to click the play button?

[deleted]
Post reply on HN