A lot of people browsing the web with Pale Moon will from time to time come across a page that isn't compatible with the browser because of the website's UI sniffing and so on and so forth. Sometimes Firefox compatibility mode helps, sometimes it doesn't.
If more non-technical users were to email the users of those websites and ask them to support Pale Moon, that'd obviously help. However, a lot of people have only a vague idea of what a site would have to do in order to properly support Pale Moon and will wind up giving instructions that aren't specific enough to be useful or are flat out wrong (Due to a misunderstanding). Even website designers may not be familiar with the browser and how to optimally support it, and may be unwilling to do a lot of legwork to find out due to our relatively small market share..
What if there were a webpage at palemoon.org that we could email site owners a link to that specifically laid out in technical detail how a website owner would go about adding support for Pale Moon to his or her website? Maybe with an email address for a developer at the bottom who could be contacted if a site owner has further questions? Users could potentially even post this link in message forum discussions elsewhere or in comment sections or feedback modules when the subject comes up.
Suggestion: "How Websites Can Support Pale Moon Users" Page
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.
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.
-
somdcomputerguy
- Lunatic
- Posts: 385
- Joined: 2014-02-23, 17:25
- Location: Greenbrier County, West Virginia
Re: Suggestion: "How Websites Can Support Pale Moon Users" P
The page could start with You're a dumbass and you call yourself a webmaster.What if there were a webpage at palemoon.org that we could email site owners a link to that specifically laid out in technical detail how a website owner would go about adding support for Pale Moon to his or her website?
-bruce /* somdcomputerguy.com */'If you change the way you look at things, the things you look at change.'
-
CharmCityCrab
Re: Suggestion: "How Websites Can Support Pale Moon Users" P
LOL. Well, the truth is, there are a lot of novice webmasters out there. You can head over to a lot of these domain registrar and hosting sites and get yourself a domain for $10-$20 a year along with $5-$10 a month hosting and, with minimal technical skills, you're in business. Even some slightly more advanced webmasters may have just learned to support the major browsers because that's what was in the book they read or the class they took, or that's what the software they use supports.somdcomputerguy wrote:The page could start with You're a dumbass and you call yourself a webmaster.What if there were a webpage at palemoon.org that we could email site owners a link to that specifically laid out in technical detail how a website owner would go about adding support for Pale Moon to his or her website?
Pragmatically, it makes sense (To me anyway), to not assume everyone knows what the issues are and how to address them and is just not addressing them because they don't want to, but to just come into it assumption free and figure some people might be persuadable if they better understood why there is a need to do something and what exactly is involved in doing it.
Meeting people where they are is generally a better idea than meeting them where you think they should be. If you go where you think they should be and they aren't there, you're going to have a tough time finding each other.
-
New Tobin Paradigm
Re: Suggestion: "How Websites Can Support Pale Moon Users" P
Back in my day (Good opening eh?),
Those who were learning on their own were encouraged to test websites in every browser.. Be it IE, Netscape, Opera, IE shells including AOL, Even a text mode browser.. And try to make decisions that didn't exclude anyone without good cause.. Though text mode got the shaft first when things like JS and Flash became popular.
My personal policy is and has been for 15 years now.. Design wise target Gecko but try to do your very best with other browsers.. Fallbacks or minor compromises to get as good effect as you could.. However, functionally? Make it work in everything regardless..
Yeah my sites may have not had some of the improved design touches like rounded corners, gradients, or transparency on say.. IE or Opera at the time.. But it didn't look radically different without those elements and didn't hinder functionality.. It all still worked the same..
PERHAPS, we should head back to that way of doing things
Those who were learning on their own were encouraged to test websites in every browser.. Be it IE, Netscape, Opera, IE shells including AOL, Even a text mode browser.. And try to make decisions that didn't exclude anyone without good cause.. Though text mode got the shaft first when things like JS and Flash became popular.
My personal policy is and has been for 15 years now.. Design wise target Gecko but try to do your very best with other browsers.. Fallbacks or minor compromises to get as good effect as you could.. However, functionally? Make it work in everything regardless..
Yeah my sites may have not had some of the improved design touches like rounded corners, gradients, or transparency on say.. IE or Opera at the time.. But it didn't look radically different without those elements and didn't hinder functionality.. It all still worked the same..
PERHAPS, we should head back to that way of doing things