Live data from Hacker News

Firefox 64 Released

hacks.mozilla.org

151–160 of 527 posts

Re: Firefox 64 Released

#151
post #104
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.

You can work around this (not ideal I know) by enabling "Low Resolution" mode for Firefox only: https://support.apple.com/en-us/HT202471

(I have the same issue and I'd like to switch to Firefox)

Re: Firefox 64 Released

#152
post #117

Earlier quoted context omitted.

I'm not. Wayland lacks a lot compared to X.[1] From the linked-to-post, it lacks: * Programmatic output configuration (xrandr, arandr, etc.) * CLI clipboard access (xsel, xclip) * Third party app launcher/window switcher (rofi, dmenu, albert, docky). * Clipboard managers (parcellite, klipper, Gpaste, clipman, etc.) * Third party screen shot/capture/share (shutter, OBS, ffmpeg, import, peek, scrot, VNC, etc.) * Color…

Those things are mostly compositor specific and not specifically a Wayland issue. For example with Sway: ​ * Programmatic output configuration swaymsg -t get_outputs # get displays swaymsg output DP-1 pos 0 0 res 1920x1080 # set displays ​ * CLI clipboard access swaymsg -t get_clipboard ​ * Third party app launcher/window switcher I use gnome-panel with Xwayland, but better than nothing ​ * Third party screen shot/ca…

No, it's fundamentally a wayland issue.

Window managers can implement their own extra protocols of course, but instead of X11 where everything was standardized and window managers didn't even have to think about it, there is no standard and window managers have to rewrite all the code for it themselves.

Re: Firefox 64 Released

#153

> We’re excited to introduce multiple tab selection, which makes it easier to manage windows with many open tabs. Simply hold Control (Windows, Linux) or Command (macOS) and click on tabs to select them. Once selected, click and drag to move the tabs as a group — either within a given window, or out into a new window. Yessss. It doesn't happen often, but the times when I open up 6-10 tabs for research but then decide…

Also being able to save them as a session would be a nice touch.

Re: Firefox 64 Released

#154

> We’re excited to introduce multiple tab selection, which makes it easier to manage windows with many open tabs. Simply hold Control (Windows, Linux) or Command (macOS) and click on tabs to select them. Once selected, click and drag to move the tabs as a group — either within a given window, or out into a new window. Yessss. It doesn't happen often, but the times when I open up 6-10 tabs for research but then decide…

In cases like this I used to open a new window and use this plugin [0] to move them fast, because dragging tabs between windows seems very finicky to me in Firefox. Hopefully with this update things will improve.

[0] https://addons.mozilla.org/en-US/firefox/addon/movetab/

Re: Firefox 64 Released

#155

Earlier quoted context omitted.

The same person who managed to make the text and background color not clash will also be able handle two scrollbar colors responsibly. Take e.g. a textarea that gains focus and has the both scrollbar and border change color, what's so terrible about that?

> The same person who managed to make the text and background color not clash Just to check, is that sarcasm? Because having those end up the same for users who use non-default colors is a _very_ common webdev mistake...

No sarcasm, and that question wasn't rhetorical either: How is a scrollbar that different from other input elements within webpages that can already be styled?

And what do you mean by using non-default colors? User stylesheets would also include scrollbar colors anyway; do you mean just setting a background but no text color (assuming a default of black, which might not be black for the user)? Don't see how this could apply to this CSS property, since it takes two colors, you either set both or none.

It seems logical to me that if you can read the text on the web page, that is, if the web dev hasn't made the common mistake that renders the text unreadable, they will set the scrollbar colors to something of similar "quality". If you can't read the text because they use CSS badly, then the scrollbar color is the least of your worries. QED?

Generally speaking, there are a lot of "common webdev mistakes", like using the giant images and scaling them down, having text and background color very close together... but we don't take that away just because some abuse it, so resisting more flexibility on those grounds doesn't strike me as so "obvious" as people seem to agree it is. If you can allow websites to hide the mouse cursor, I don't think the web will break because of this CSS property. If you don't want to see it on any page, override it in your user stylesheet, done.

Re: Firefox 64 Released

#156
post #72

I've just updated to new beta (Firefox 65.0b3) with WebRender enabled and it started showing such error in about:support: [GFX1-]: shader-cache: Shader disk cache is not supported I'm using AMD GPU and as far as I know, Mesa supports shader cache for radeonsi and radv. Does anyone know why that error is showing up?

See https://bugzilla.mozilla.org/show_bug.cgi?id=1511726

Assuming you're on non-Windows, the message is expected and not indicative of a problem. I've pushed a patch to disable it going forward. Sorry for the noise.

Re: Firefox 64 Released

#158

> We’re excited to introduce multiple tab selection, which makes it easier to manage windows with many open tabs. Simply hold Control (Windows, Linux) or Command (macOS) and click on tabs to select them. Once selected, click and drag to move the tabs as a group — either within a given window, or out into a new window. Yessss. It doesn't happen often, but the times when I open up 6-10 tabs for research but then decide…

It's the little things (: To be honest as soon as I figure out how to change all the little workflow details I currently use in Chrome, I'll be happy to switch to use Firefox more often / primarily. I love how snappy Quantum feels.

Re: Firefox 64 Released

#159
post #42
post #39

Earlier quoted context omitted.

arrrr... what they don't realize when they review their telemetry data is that most people that use this feature have turned off sharing telemetry data. Combine that with the fact that they haven't advertised the feature in the past decade and it leads to devs thinking nobody uses it.

Then perhaps you can see why telemetry is useful to responsible companies like Firefox, and maybe people who disable it have no right to complain about decisions based off telemetry data?

Then perhaps you can see why using telemetry is irresponsible.

Re: Firefox 64 Released

#160
post #39
post #34

Earlier quoted context omitted.

After installing the update it opens this page: https://support.mozilla.org/en-US/kb/live-bookmarks-migratio...

arrrr... what they don't realize when they review their telemetry data is that most people that use this feature have turned off sharing telemetry data. Combine that with the fact that they haven't advertised the feature in the past decade and it leads to devs thinking nobody uses it.

The usage stats from telemetry showed a 0.01% usage rate. Even if 99% of people that used the Live Bookmarks feature disabled telemetry that implies that 99% of Firefox users did not use the feature.
Post reply on HN