Forums for Audacity and Brave browser / Unsupported Browser error

[Sessh]

The forums for Audacity and the Brave browser (among others I can't recall now) do not load properly (scroll bar doesn't load at all and website doesn't load correctly).
https://forum.audacityteam.org/
https://community.brave.com/t/brave-sup ... rce/627441

The console output on both is basically the same thing with slight differences due to them being different websites:

Clipboard01.png

Tried in Clean Profile, no difference. Anything we can do to get around this? Is it looking for something we can implement or... lost cause?
I searched for keywords on this forum and didn't see any threads on this, so apologies if I missed them.

[Moonchild]

Discourse continues to discriminate against us. There are workarounds for this on the forum (if you search for "discourse" you should be able to find them)

[FranklinDM]

scroll bar doesn't load at all

The scrollbar issue will be fixed soon with PM 33.9.0.

[Sessh]

Ok, I was able to find that workaround. Those forums seem to at least be usable now, thanks. Scrollbar works as well.

Am I correct in gathering from what I read that a more proper fix for this is going to be a huge load of work for this very small team and is unlikely to happen as a result?

[Moonchild]

Am I correct in gathering from what I read that a more proper fix for this is going to be a huge load of work for this very small team and is unlikely to happen as a result?

As long as they keep exclusively targeting Chrome quirks (which is a moving target) instead of a broader/more agnostic use of features, it'll always remain an issue. Team size doesn't necessarily even matter in that case (other than being able to respond quicker to changes - but if those changes are unwanted anyway...)

[Sessh]

Am I correct in gathering from what I read that a more proper fix for this is going to be a huge load of work for this very small team and is unlikely to happen as a result?

As long as they keep exclusively targeting Chrome quirks (which is a moving target) instead of a broader/more agnostic use of features, it'll always remain an issue. Team size doesn't necessarily even matter in that case (other than being able to respond quicker to changes - but if those changes are unwanted anyway...)

Off-topic:
Well, with Google's insistence on killing off uBO in Chrome and it's forks not doing that, one can hope Chrome's market share continues to decline as users seek alternative browsers. Over 30 million users is nothing to shake a stick at. Maybe things will start to change. Big maybe, though.

[Moonchild]

Off-topic:

Well, with Google's insistence on killing off uBO in Chrome and it's forks not doing that, one can hope Chrome's market share continues to decline as users seek alternative browsers.

That will do absolutely nothing as long as those other browsers all use the Chrome engine anyway.

[adoxa]

As long as they keep exclusively targeting Chrome quirks

The only test failing is support for aspect-ratio.

[Sessh]

The only test failing is support for aspect-ratio.

I saw that too while looking through the forum, but it seems fixing that would be a massive undertaking, yes?

[Moonchild]

The only test failing is support for aspect-ratio.

...from the features they test for, yes.
But if Discourse is designed around Blink, then it will likely also assume a feature set with other things we may not support or support differently.

[adoxa]

I saw that too while looking through the forum, but it seems fixing [aspect-ratio] would be a massive undertaking, yes?

Sure, I just wouldn't call it a "Chrome quirk".

But if Discourse is designed around Blink, then it will likely also assume a feature set with other things we may not support or support differently.

Possibly, but since all the filter does is remove browser-detect (which only fails because of that one aspect) and sites seem fine, once aspect-ratio is implemented Discourse should no longer be a major issue.

[Moonchild]

I just wouldn't call it a "Chrome quirk".

Fair! But it hasn't just been that one thing; it's been other things in the past and probably more other things in the future.

Possibly, but since all the filter does is remove browser-detect (which only fails because of that one aspect) and sites seem fine, once aspect-ratio is implemented Discourse should no longer be a major issue.

That misses the entire point though. If they test for something that isn't exactly required for it to function, then why test for it to begin with? Other than excluding classes of browsers, of course.

[Gemmaugr]

Discourse will also need SubGrid and Relative Color Syntax. (Tried to view the page again, from my link, but it also requires Performance Observer. With JS off, it seems they've also added Import Maps?)

viewtopic.php?f=70&t=32336#p262258

[Moonchild]

Well, I don't see all of that that being done on short notice. But that underlines the other part of my point, wanting the full Blink feature set and whatever is being added this month. Choosing discourse is just choosing something only mainstream can keep up with.

[franstam]

whats wrong with this forum software that palemoon forums is using? it works the same whether on a phone or pc, and is much better supported than whatever discourse is

[moonbat]

whats wrong with this forum software that palemoon forums is using?

Nothing. Re-read the original post.

[Moonchild]

whats wrong with this forum software that palemoon forums is using?

Nothing. Re-read the original post.

I'm pretty sure that was just a generic question, not specific to this particular set of websites.

But.. the answer is just that there's multiple things webmasters can choose to use for their community interaction - discourse is unfortunately "trendy" while it's aiming specifically at a small handful of browser variants. And it's a scripting mess >.>
But it's still the webmaster's choice whether they want to use it or phpbb or proboard or matrix or...