What do you think about the Web Compat project?

[Lunokhod]

https://webcompat.com/about

"Webcompat.com is developed by volunteers and supported by Mozilla. This site is an open invitation for all web users, developers and browser vendors to get involved in the web compatibility effort. Our goal is to make it easy to report and view compatibility problems for any part of the web."

I read about this project. Sometimes issues appear on this forum which seem relevant, and it might give more incentive for site maintainers to fix issues if the Web Compat project contacted them rather than just an individual, if there was a problem getting a response.
But it has a connection to Mozilla. They also use a bot to test random websites for Firefox compatibility, so a lot of the reports are created by that. The project has not been mentioned much on this forum so I wondered what people here thought about it.

[moonbat]

Compatibility with what though? HTML5 being a 'living' standard now, it's a moving target. Seems like code for 'make sure your site works in the top two browsers in the market'.

[Lunokhod]

According to the site documentation they are most interested in things that work in one browser but not another:

"Have you found something and aren't sure if this is the right place to report that issue? Try to reproduce the issue in another browser. Does it work there? Try again in the first one. Still an issue? Congratulations! You found one. Send it in! "
" After moving the issue to diagnosis, one member of our community digs into the code to figure out what’s causing the compatibility issue and or files bugs with browser vendors.
Sometimes it might also be possible the relevant web technology standard is underspecified or browsers implement it in different ways. We help to provide feedback and make suggestions to the specifications to make them stable for everyone.
Reaching Out
After finding what is causing the web compat issue, there are different ways to proceed. If the issue is caused by incompatible code, the community tries to contact the site owner or company behind it and suggest a fix."

If it doesn't work in Pale Moon but does work in FF / Chrome then that's what they want to know about.
It seems only those browsers have web compat reporting extensions, others must use the form. However, the site also says:

"Other browser vendors are welcome to provide a way to automatically report issues to webcompat.com in a similar fashion in their pre-release versions. Open an issue on the webcompat.com project."
https://github.com/webcompat/webcompat.com/issues/new

So it looks like Pale Moon would be welcome to join those 2.

[moonbat]

As I suspected. It's not about adhering to a standard, because then it would be browser agnostic.

[Moonchild]

I don't think there's much use in starting to report there. Do you see any other minor browsers listed on that site, or is it just comparing between the biggest mainstream giants?

[moonbat]

I don't think there's much use in starting to report there. Do you see any other minor browsers listed on that site, or is it just comparing between the biggest mainstream giants?

Probably only Chrome and Firefox. All others are derived from Chrome anyway. And as I said, time was when compatibility meant adhering to the defined HTML standard, and if they cared about that that's what they should've provided.

[Lunokhod]

The only mention of using webcompat on this forum was from KNTRO. Apparently it was successful for all 4 issues reported on GitHub, e.g.:
https://github.com/webcompat/web-bugs/issues/158
And the webcompat-bot compared to Pale Moon earlier this year here:
https://github.com/webcompat/web-bugs/issues/31125
Searching the mailing list did not reveal anything from Pale Moon but there was some contact with Opera, who seem to do their own bug tracking but cooperate with webcompat, so there must be various levels of involvement possible.

Of course, reporting things on the Pale Moon forum is usually very effective. But if no resolution was achieved then it could be another possibility to explore.

[New Tobin Paradigm]

Yeah it doesn't seem so much (but there is some) about making websites compatible with browsers but making browser compatible with Chrome's featureset which of course will mean better compatibility with websites because everyone is Chrome or Pseudo-Chrome (webkit and gecko).

Mozilla and their people have also been very hostile towards us before. Given their now full on techleft social justice soros globalist chinese stance of diverse conformity.. I don't think any actual cooperation is possible except in secret or obscurity with the dwindling few who are from the old days.

If you do take it upon yourself to talk to them.. remember to use gender neutral pronouns!

[van p]

remember to use gender neutral pronouns!

Should we even be using pronouns at all? Doesn't that objectify people--we, you, they, etc.? And maybe we shouldn't even be talking about people. What about the animals--it's not right to leave them out, that's not diverse.

[Mæstro]

This Web Compatibility project is twenty years late. HTML 4.01 was implemented in 1999, and remained a firm standard until Google's gentle taps became hard blows. Browsers' struggle to become compatible with 4.01 seem to have ended about 2003 or so. If developers could keep to the rather clear guidelines that were established at this relatively early time in Web history, there would be much fewer compatibility problems. (The problem that mobile Web pages must be different to desktop probably cannot be reconciled, except in the traditional method of having a separate mobile version of the Web site.)