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

251–260 of 527 posts

Re: Firefox 64 Released

#251

Post by chipotle_coyote »

FPGAhacker wrote: post #213
QML wrote: post #199

Earlier quoted context omitted.

Doesn’t Safari prevent videos from auto-playing?

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

It's an option under "Websites" in "Preferences"; the options are "Never Auto-Play," "Always Auto-Play," and "Stop Media with Sound." The latter is the default. You can set a default for all web sites, and add override settings for specific sites.

(There's actually a wealth of stuff in this preference tab: you can set defaults and per-site overrides for content blockers, page zoom levels, camera and microphone, defaulting to "Reader View" for particularly annoying sites, and so on.)

Re: Firefox 64 Released

#252

Post by halfjoking »

daleharvey wrote: post #228
nothrabannosir wrote: post #225

Earlier quoted context omitted.

Even for YouTube?

Yes, we dont have any whitelist / blacklist of sites we treat differently

I hope there's a bigger backlash to Google blacklisting/whitelisting certain features on websites they deem worthy/unworthy.

It's one thing to discriminate against certain sites in Search, where Google owns the webpages and servers. But to discriminate against the open web so that their services have an advantage over startups and smaller publishers is beyond unethical. At this point they're starting to act like a monopolistic ISP and should be called out for it.

Re: Firefox 64 Released

#253

Post by floatboth »

sprash wrote: post #203
mixmastamyk wrote: post #105

Earlier quoted context omitted.

I'm happy someone is using it however, as that will encourage many shortcomings to be addressed.

In my experience X11 has zero shortcomings compared to Wayland. The code might be ancient and arcane at some points but the performance and features (hello "ssh -X") are actually far superior. Why do we need Wayland?

Superior performance? Like when windows take a whole second to appear because the protocol is synchronous and the server is busy doing something else? :)

Wayland makes lots of things possible: multi-monitor HiDPI, touchpad gestures like pinch to zoom (just like Macs could do ages ago), touchscreen support that's actually independent of the mouse pointer instead of always dragging it along… and there's finally no goddamn screen tearing. Every frame is perfect™.

Re: Firefox 64 Released

#254

Post by pmoriarty »

trulyrandom wrote: post #235
sprash wrote: post #203

Earlier quoted context omitted.

In my experience X11 has zero shortcomings compared to Wayland. The code might be ancient and arcane at some points but the performance and features (hello "ssh -X") are actually far superior. Why do we need Wayland?

I have never been able to get a tearing-free experience with X11, and I've tried everything to fix it. Meanwhile Wayland is butter smooth out of the box on the same hardware. Security is another obvious advantage of Wayland.

Just another data point: I've never experienced screen tearing in the decades that I've used X.

Also, when I run X just for myself on my own laptop, what security issues do I have to worry about with X that I don't have to worry about with Wayland?

Re: Firefox 64 Released

#255

Post by AsyncAwait »

gpm wrote: post #152
iod wrote: post #117

Earlier quoted context omitted.

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.

> No, it's fundamentally a wayland issue.

It's not an "issue". It's a design decision.

As another example, Linux doesn't have just one desktop environment, like Windows or MacOS, would you say that's an "issue", even if it's a deliberate decision?

Re: Firefox 64 Released

#256

Post by oblio »

detaro wrote: post #183
AbuAssar wrote: post #179

Earlier quoted context omitted.

even simpler in firefox: [1] open youtube.com [2] right click on the search bar and select "Add a keyword for this search" [3] in the dialog enter the character "y" as the keyword. [4] done! now to search youtube from the address bar just enter y followed by the search terms!

I'd argue that manually adding each site individually is not "even simpler".

Does Chrome do it for random site searches? Not for Google properties.

Re: Firefox 64 Released

#257

Post by AsyncAwait »

sprash wrote: post #203
mixmastamyk wrote: post #105

Earlier quoted context omitted.

I'm happy someone is using it however, as that will encourage many shortcomings to be addressed.

In my experience X11 has zero shortcomings compared to Wayland. The code might be ancient and arcane at some points but the performance and features (hello "ssh -X") are actually far superior. Why do we need Wayland?

Performance on Wayland is waaay better for me. Also, the security model is far superior.

Re: Firefox 64 Released

#259

Post by rosser »

cpmsmith wrote: post #239
jillesvangurp wrote: post #220

Earlier quoted context omitted.

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 an…

Anecdotal, but I've found it happens when image scaling by a factor other than 2. Affects my setup of a 4K display at 2650x1440 effective resolution, or 1.5x scaling.

Exactly this. I run at 1920x1080 effective resolution on my 15" rMBP, and 1680x945 on my 13". I see the issue on both.

When I switch to the "default" scaling (1440x900 and 1280x800, respectively), it stops. Only the 15" has a discrete GPU, eliminating that as potentially causal.

The "problem" scaling is 1.5x. The default is 2x.

Re: Firefox 64 Released

#260

Post by yjftsjthsd-h »

TekMol wrote: post #108

Does it support hardware accelerated video playback on Linux now? I have been waiting for this feature for I don't know how many years. Every Firefox release, I am reminded of this xkcd comic: https://xkcd.com/619/

To be fair, that particular comic is slightly funny because we have now outlived Flash video.
Post reply on HN