Web compatibility suggestion

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
User avatar
Kolusion
Hobby Astronomer
Hobby Astronomer
Posts: 22
Joined: 2023-07-17, 13:20

Web compatibility suggestion

Unread post by Kolusion » 2023-07-17, 14:53

I suggest Pale Moon use native web compatibility as its default web compatibility setting. Having Firefox as the default setting belittles Pale Moon. Plus, it goes again Pale Moon's aim which includes "common-sense web standards and specifications in its implementation (with minimal compromise)". This feature by definition supports the idea that web developers should aim for user agents and not web standards, which goes against Pale Moon's aim.

User avatar
therube
Board Warrior
Board Warrior
Posts: 1651
Joined: 2018-06-08, 17:02

Re: Web compatibility suggestion

Unread post by therube » 2023-07-17, 16:12

If websites used "common-sense web standards and specifications...'.
Alas, they don't.
So there has to be some sort of compromise. And if that means having "firefox" in ones UA for a better overall UX...

User avatar
Trippynet
Fanatic
Fanatic
Posts: 238
Joined: 2014-06-03, 20:21
Location: UK

Re: Web compatibility suggestion

Unread post by Trippynet » 2023-07-18, 09:54

Kolusion wrote:
2023-07-17, 14:53
I suggest Pale Moon use native web compatibility as its default web compatibility setting. Having Firefox as the default setting belittles Pale Moon. Plus, it goes again Pale Moon's aim which includes "common-sense web standards and specifications in its implementation (with minimal compromise)". This feature by definition supports the idea that web developers should aim for user agents and not web standards, which goes against Pale Moon's aim.
The problem is that this was tried some time back if I recall and the result was a *lot* of broken websites complaining that "your browser isn't supported", so the default was changed back again. It was just too disruptive. It's a noble aim for website developers to target features/standards instead of user agents, but in reality many still sniff the UA and throw a hissy fit, and you can't force them to change their ways.

BenFenner
Astronaut
Astronaut
Posts: 588
Joined: 2015-06-01, 12:52
Location: US Southeast

Re: Web compatibility suggestion

Unread post by BenFenner » 2023-07-22, 17:58

You make this suggestion (and keep linking to this thread elsehwere) like we don't all want the same thing, and have been wanting it for a long time. Of course, in a vacuum, we all want the user agent set to a Pale Moon original. However it has been attempted multiple times in the past, and as recent as a year or two ago. It still causes a few too many problems to be worth it.

Get a job at a web development shop and write some browsers agnostic sites to stem the tide. That's what I'm doing anyway...

Or better yet, make the UA switch to your own browsers(s) and start hammering the support channels of any sites you find that are prejudice against a pure Pale Moon user agent.