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

211–220 of 527 posts

Re: Firefox 64 Released

#211

Post by aembleton »

throwaway453405 wrote: post #188
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…

Create a Search Bookmark 1. Got to the Bookmark Library and Right Click > New Bookmark and fill it as follows: Name: YouTube Search Location: https://www.youtube.com/results?search_query=%s Keyword: you 2. Click Add 3. Now in the Location bar type "you apples" and apples will be searched on YouTube. I use this for a lot of sites with search inputs. I often do searches using ddg of sites I visit with forums or other b…

I even use it to quickly reach Jira tickets that I know the number of. Just modify the URL with a Bookmark.

Re: Firefox 64 Released

#212

Post by Asooka »

moosingin3space wrote: post #38

Kind of a niche thing to comment on, but this release lands a commit I made that enables XDG desktop portals support in Firefox. If you're on KDE Plasma, you can run Firefox with the environment variable `GTK_USE_PORTAL=1` set and it will use KDE file selection dialogs.

It might be niche in the grand scheme of things, but for me this is an incredible improvement on my usage of Firefox. This was honestly one of the few things that Chrome did better. Firefox was the only program that I use every day that forced me to use the GTK file selection dialog. Thank you very much!

Re: Firefox 64 Released

#213

Post by FPGAhacker »

QML wrote: post #199
mancerayder wrote: post #180

What's the status of the cat and mouse game being played with autoplay video being forced on and new options needing to be hunted down? First Chrome forced it on, because EvilCorp's business model is around a forced-open-eyelid philosophy of advertising revenue from unstoppable impressions. Next I moved to Firefox, which in an update a few months ago changed the autoplay option to be on, removed the config attribute…

Doesn’t Safari prevent videos from auto-playing?

Not in my experience, although I thought it was supposed to.

Re: Firefox 64 Released

#214

Post by dilap »

omnimus wrote: post #88
dilap wrote: post #60

Still no bounce scroll on mac makes this dead in the water for me. Folks, the UI look and feel stuff really matters. You can't treat a platform like a second-class citizen and hope to gain widespread adoption.

Interesting. I am ux designer and i never thought people care about this or even realize there is difference. I mean actually quite opposite lot of people i know were confused from the movements first time this feature landed in safari. Anyway surely this is not a showstopper. I mean it is not functional in any way.

Scrollbars that auto-hide and bounce scrolling are standard behavior for any macOS application.

Apps that don't do this both look and feel weird.

Maybe not a showstopper if Firefox were offering unavailable-anywhere-else behavior, but it's completely natural and predicable that users will migrate to one of the other two major browsers that care enough to make themselves fit in w/ the system they are running on.

Re: Firefox 64 Released

#215

Post by Bjartr »

Doctor_Fegg wrote: post #22

> The CSS Scrollbars Level 1 spec standardizes features for setting scrollbar width and color I would like these features to be standardised to hands-off-my-fricking-scrollbars. I’m fed up with impossible-to-grab 1px-wide scrollbars because “everyone has trackpads”. No, they don’t.

You could use a css customizing extension or create your own userscript to force all scrollbar related css attributes to the `inital` value.

Re: Firefox 64 Released

#216

Post by gnicholas »

bzbarsky wrote: post #119
gnicholas wrote: post #80

Earlier quoted context omitted.

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…

If Brave is running circles around Chrome for you in general, that's likely a result of cognitive bias, since last I checked it's the same rendering engine. For pageloads Brave might do better if it blocks various stuff by default, of course.

> if it blocks various stuff by default

This is one of the key differentiating factors of Brave. Maybe next time don’t lead with accusations of cognitive bias.

Re: Firefox 64 Released

#217

Post by ryacko »

mancerayder wrote: post #180

What's the status of the cat and mouse game being played with autoplay video being forced on and new options needing to be hunted down? First Chrome forced it on, because EvilCorp's business model is around a forced-open-eyelid philosophy of advertising revenue from unstoppable impressions. Next I moved to Firefox, which in an update a few months ago changed the autoplay option to be on, removed the config attribute…

Autoplay pads ad viewing numbers.

Ad firms are probably paying Mozilla to include it.

Re: Firefox 64 Released

#218

Post by AnaniasAnanas »

dictum wrote: post #135
Doctor_Fegg wrote: post #22

> The CSS Scrollbars Level 1 spec standardizes features for setting scrollbar width and color I would like these features to be standardised to hands-off-my-fricking-scrollbars. I’m fed up with impossible-to-grab 1px-wide scrollbars because “everyone has trackpads”. No, they don’t.

Time for FF's balance of configurability and reasonable defaults to shine: the about:config properties to edit are `layout.css.scrollbar-color.enabled` and `layout.css.scrollbar-width.enabled`.

I am pretty sure that changing it would be a bad idea if you care about your privacy.

Re: Firefox 64 Released

#219

Post by daleharvey »

mancerayder wrote: post #180

What's the status of the cat and mouse game being played with autoplay video being forced on and new options needing to be hunted down? First Chrome forced it on, because EvilCorp's business model is around a forced-open-eyelid philosophy of advertising revenue from unstoppable impressions. Next I moved to Firefox, which in an update a few months ago changed the autoplay option to be on, removed the config attribute…

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, or pocket

Re: Firefox 64 Released

#220

Post by jillesvangurp »

jasin wrote: post #104
nindalf wrote: post #74

Earlier quoted context omitted.

To be clear, this doesn't affect all macOS users. My battery reliably lasts a whole day with Firefox running throughout. That said, the subset of users who are affected, like you, suffer a lot - low prevalence, high impact.

In my case, CPU usage goes to the roof if I use a scaled resolution instead of the default one. If that is the case with all macOS users with non-default resolution, I wouldn't call it low prevalence.

Not an issue for me. I have a imac 5K and a retina mac book pro. Both with image scaling on by default. I think most recent macs have retina now.

I use Firefox exclusively and have done so for the last 2 years or so. This sounds like it could be a driver issue for specific macs. Both my macs have AMD Radeon chipsets & quad core i7s.

Anyway, I'm sure this issue is real. Bugzilla ticket numbers probably exist for it and might be more helpful than vague complaints about things being slow.

Of course some web sites are a bit unreasonably javascript heavy these days. The downside of a large screen is that pushing a lot of pixels around is not free. Usually closing any offending tabs immediately restores any cpu usage I see. I'd suggest using the new task manager thingy (page menu->more->task manager)

Post reply on HN