this post was submitted on 29 Dec 2023
500 points (97.2% liked)

Hacker News

4123 readers
2 users here now

This community serves to share top posts on Hacker News with the wider fediverse.

Rules0. Keep it legal

  1. Keep it civil and SFW
  2. Keep it safe for members of marginalised groups

founded 1 year ago
MODERATORS
 

There is a discussion on Hacker News, but feel free to comment here as well.

you are viewing a single comment's thread
view the rest of the comments
[–] platypus_plumba@lemmy.world 1 points 10 months ago (1 children)

I've had many problems with Firefox that always push me back to Chrome. It seems some web pages are only created with Chrome in mind. I really don't know about browser specs but I'm guessing a front-end app must have a lot of "if chrome, then; else if Mozilla then;" logic to handle specific browser interfaces or features.

Apparently some apps don't care about Mozilla and they just don't work. It's also pretty hard to tell that the issue is Mozilla, it takes me like 15m to switch to chrome and then "ahhhh.... it was the browser".

I really want to help Mozilla by using it, but I just can't under those conditions.

[–] fifisaac@lemmy.world 4 points 10 months ago (2 children)

What sites are these? I've not had this in years and when there is problems the site normally says unsupported browser rather than leaving me to guess

[–] platypus_plumba@lemmy.world 2 points 10 months ago

Mostly payment platforms

[–] DirtyCNC@lemmynsfw.com 1 points 10 months ago* (last edited 10 months ago)

Other than YouTube, which purposefully slows Firefox down, I only ever encountered one webpage in years where the issue was 100% “caused” by my browser choice – the left pane (lesson list) in my school’s tutoring platform would not scroll due to what I assume was a trivial HTML oversight. After reporting the issue, they insisted that they would not support browsers other than ones based on Chromium and Safari and tried to convince me to switch. I don't have access to the site anymore and I did not understand web development at all back then so I could not create a patch myself; I just worked around the issue using a very tall, zoomed-out “mobile view” to reach the off-screen buttons.