Important sites disfunctional on PaleMoon

Indigoprophet · Unread post by **Indigoprophet** » 2022-04-01, 14:53

Operating system: Windows 10
Browser version:30.0.1
32-bit or 64-bit browser?:64
Problem URL:many
Browser theme (if not default):default
Installed add-ons:CPU & Memory Usage Statusbar
Installed plugins: (about:plugins):Adobe Acrobat, Microsoft Office 2016

If possible, please include the output of help->troubleshooting information (as text):

Hello!
I've come across several situations where some sites are not working properly in PaleMoon and it seems like the amount of those is growing bigger. And these sites are quite important. Here are a couple of examples:
https://imgur.com/a/4y8wJ3x
Also there are cases when a link must open an app like MS Teams, but it doesn't (while other browsers do). And these are just a couple of examples, actually there are more. And this has been going on for several versions already.
So my question for the developers is as follows: are you going to fix it at all or do you consider it normal that certain sites are not working?

gepus · Unread post by **gepus** » 2022-04-01, 15:44

@Indigoprophet
Very kind of you spending your precious time to register for informing us that some sites don't work.
As a simple user I'd recommend to use a browser that suits your needs.

BenFenner · Unread post by **BenFenner** » 2022-04-01, 16:21

Report the issue to Github, Instagram, and StackOverflow. I've done so with 2 of those 3 already, but the more they hear from us the better.
Those sites should work on a standards compliant browser. They are using draft standard technology. Request they revert to standards compliance.

Indigoprophet · Unread post by **Indigoprophet** » 2022-04-01, 16:52

What is draft standard?
Actually I suspected that the standards are not fully implemented in Pale Moon. Some time ago I also tried to input a date into the form field of the appropriate type and it didn't show me the calendar like Firefox for example does. Also I launched a standard React app with rotating logo and there was actually no rotation, so the corresponding animation is not implemented. I guess this is pretty standard stuff, isn't it?

coffeebreak · Unread post by **coffeebreak** » 2022-04-02, 08:05

Indigoprophet wrote: ↑
2022-04-01, 14:53
several situations ... some sites are not working properly in PaleMoon

1. Compatibility problems should be raised in the Web Compatibility Support board - not here.

2. Don't combine multiple problem sites (or in other cases, multiple support issues) in the same thread.

3. Don't open a new thread if the same issue with the same site already has an open thread. If you want to post on that matter, do it in the thread that's already open. Which leads to the next point...

4. Search the forum before choosing to post. And read and familiarize yourself with any existing discussion on the issue that concerns you. Get acquainted, if you're not already, with the forum's advanced search page.

5. Finally, don't open threads for the purpose of venting irritation over broken websites, or to "put pressure" on the developers because you imagine that somehow this will "get them" to fix things you believe they otherwise wouldn't.
It won't help get things fixed, it only gets people annoyed.

Indigoprophet wrote: ↑
2022-04-01, 14:53
imgur.com

imgur (forum search)
Read through this thread for some workarounds.

Indigoprophet · Unread post by **Indigoprophet** » 2022-04-06, 12:29

Oh, you like it step by step, don't you? So be it:

1. Compatibility problems should be raised in the Web Compatibility Support board - not here.

Now that I know that you call it compatibility problems - there I'll go.

2. Don't combine multiple problem sites (or in other cases, multiple support issues) in the same thread.

I will combine multiple issues if these issues have a common nature.

3. Don't open a new thread if the same issue with the same site already has an open thread. If you want to post on that matter, do it in the thread that's already open. Which leads to the next point...

See the next point.

4. Search the forum before choosing to post. And read and familiarize yourself with any existing discussion on the issue that concerns you. Get acquainted, if you're not already, with the forum's advanced search page.

I know pretty well how search works, but it's impossible to use it if you don't know exactly with what words your issue is described, which was the case here.

5. Finally, don't open threads for the purpose of venting irritation over broken websites, or to "put pressure" on the developers because you imagine that somehow this will "get them" to fix things you believe they otherwise wouldn't.
It won't help get things fixed, it only gets people annoyed.

And finally, I'm not "venting irritation" or "putting pressure" here, I'm raising a critical issue, which is the only one that must bother the developers - that the browser doesn't browse. And the purpose of this forum is collaboration between users and developers on solving issues like that. This is what I've come for, and not to listen to your foolish frame-ups. I'm pretty sure the developers will answer for themselves without an advocate.

I'm making it final for this thread - there will be no more answers.

P. S. Imgur works fine for me.

ron_1 · Unread post by **ron_1** » 2022-04-06, 12:58

Indigoprophet wrote: ↑
2022-04-06, 12:29
I will combine multiple issues if these issues have a common nature.

Just because two or more issues have the same "symptoms" does not mean they have the same cause.

somdcomputerguy · Unread post by **somdcomputerguy** » 2022-04-06, 14:11

Off-topic:

ron_1 wrote: ↑
2022-04-06, 12:58

Indigoprophet wrote: ↑
2022-04-06, 12:29
I will combine multiple issues if these issues have a common nature.
Just because two or more issues have the same "symptoms" does not mean they have the same cause.

That's like a deja vu vapin' echo or something!

Unread post by **Moonchild** » 2022-04-06, 14:22

Indigoprophet wrote: ↑
2022-04-06, 12:29
I'm raising a critical issue, which is the only one that must bother the developers - that the browser doesn't browse.

My daily multi-hour use of the browser solidly shows that, in fact, it does.

Without specific details about the "not browsing" (when? where? how?) we can't help.
If for your web use the browser is causing too many issues, then please use a different web browser that suits your workflow better. The current state of the web is actually simple: "If you're not using the Chromium engine implementation, then not all websites will work*". We can't wave a magic wand and suddenly have those chrome-targeted websites work (and that magic wand would likely not work unless we'd become a chrome clone ourselves)

* and even on Chromium not all websites work ;P

Nigaikaze · Unread post by **Nigaikaze** » 2022-04-06, 15:22

Indigoprophet wrote: ↑
2022-04-06, 12:29
I'm making it final for this thread - there will be no more answers.

Here are two more answers for you. #1:

BenFenner wrote: ↑
2022-04-01, 16:21
Report the issue to Github, Instagram, and StackOverflow. I've done so with 2 of those 3 already, but the more they hear from us the better.

#2:

Indigoprophet wrote: ↑
2022-04-01, 14:53
Browser version:30.0.1

Roll back to version 29.4.5.1, which is the current version of Pale Moon. Version 30.x has been recalled due to multiple problems with it.

Pallid Planetoid · Unread post by **Pallid Planetoid** » 2022-04-07, 01:01

Indigoprophet wrote: ↑
2022-04-01, 16:52
What is draft standard?...

This is how I would interpret the phrase (as contrasted to the phrase "standards compliance" on the other end of the spectrum of web application development).

In my opinion, all you have to do is consider the meaning of the words used:
The word "draft" connotes that which is "preliminary" (as defined in the dictionary) hence inherently not what would be considered a "standard" (as defined in the dictionary as quote: "something considered by an authority or by general consent as a basis of comparison; an approved model.")

Browsers (i.e. Google Chrome and others who follow along) should for the good of the public stop using "draft standard technology" (that is comprised of a "preliminary" application of browser development) which is increasingly commonplace unfortunately. Instead, browsers should be more responsible by striving for "standards compliance" as much as possible.

What is "Standards Compliance"? - I presume it is best defined as the following:
In regards to what is generally considered "recommended standards" that define Web Technologies, we have the W3C published Recommendations, that are in general considered what we would call Web Standards (aka "Standards Compliance") of which entails what the Pale Moon Project (as an outlier in the world of browsers) is presumably at all times attempting to maintain as much as possible.

This is what we should expect and want "as much as possible"...

(conforming to this promotes fair and equal opportunity and most importantly a level of consistency across the spectrum of all browsers equally - a foundation that all users can hence depend upon)

This is just one of the reasons (among many, i.e. a heavy focus on "security" and "privacy" as well etc. etc.) why I will always stand by Pale Moon! (even though, to be fair, I have to say, hasn't always been reciprocal in regards to my personal experience on the forum over the years - but that's another story and I always prefer to avoid the "negative")

Indigoprophet · Unread post by **Indigoprophet** » 2022-04-07, 10:08

Indigoprophet wrote: ↑
2022-04-06, 12:29
Now that I know that you call it compatibility problems - there I'll go.

I went to the specified thread and posted this question. It was most relevant there as the answer to it would explain the reason of this mess with different sites in one place. Instead of posting this answer the admin closed the thread on the pretext that it's intended for particular sites only, not general questions. Considering the name of that forum branch (Web Compatibility Support board), this pretext looks not only stupid, but also like an attempt to pipe me down. It that's the case, the question is why?

And as I didn't receive the answer in the appropriate branch, I have to continue with it here. So:

My daily multi-hour use of the browser solidly shows that, in fact, it does.
Without specific details about the "not browsing" (when? where? how?) we can't help.

Don't quibble over words - the initial post clearly explained what I meant - that problems with browsing sites arise too often.
And... without specific details? Are you serious? I provided some examples in that same initial post and even more examples in Compatibility branch. And I can repeat them here:
https://imgur.com/a/4y8wJ3x
https://imgur.com/a/tpRKVli
The info on these screenshots is enough to find out what's wrong.

If for your web use the browser is causing too many issues, then please use a different web browser that suits your workflow better.

That's not an answer of a developer who cares for the quality of his product. If you're making a browser that is suitable for practical use, not a toy to play with occasionally, then you are meant to seek solutions for such problems.

The current state of the web is actually simple: "If you're not using the Chromium engine implementation, then not all websites will work*". We can't wave a magic wand and suddenly have those chrome-targeted websites work (and that magic wand would likely not work unless we'd become a chrome clone ourselves)

I see what you mean, but as far as I know this is not true. I've tried those sites on Firefox using Gecko (which is not Chromium) and Edge using some successor of Trident (not Chromium either) and they do work there. But they don't work in Pale Moon. Google's interest in replacing common web standard with their own for making everyone migrate to their browser and thus gaining access to their browsing data is clear. But how do you explain this issue for non-Chromium browsers?

ron_1 · Unread post by **ron_1** » 2022-04-07, 11:20

Indigoprophet wrote: ↑
2022-04-07, 10:08
And... without specific details? Are you serious? I provided some examples in that same initial post and even more examples in Compatibility branch. And I can repeat them here:
https://imgur.com/a/4y8wJ3x
https://imgur.com/a/tpRKVli
The info on these screenshots is enough to find out what's wrong.

No it's not. How about on the menu bar going to Tools >> Developer Tools >> Web Console for some "specific details" you can post here? Just saying something doesn't work and showing screenshots isn't enough. Here's that info from steelline.by. (I'm no expert, but it looks like either lazy or incompetent web design. The line SyntaxError: invalid regexp group is probably the issue here.)

Code: Select all

"Download the React DevTools for a better development experience: https://fb.me/react-devtools"  
app.min.js:94904:9
"Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: SideEffect(NullComponent)"  
app.min.js:69998:5
Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in DiscountDemo (created by Index)
    in div (created by Index)
    in Index (created by Context.Consumer)
    in Connect(Index) (created by withI18nextTranslation(Connect(Index)))
    in withI18nextTranslation(Connect(Index)) (created by component)
    in component (created by Context.Consumer)  
app.min.js:69998:5
Warning: Failed prop type: Invalid prop `sort` of type `function` supplied to `CatalogGrid`, expected `string`.
    in CatalogGrid (created by withI18nextTranslation(CatalogGrid))
    in withI18nextTranslation(CatalogGrid) (created by Catalog)
    in main (created by Catalog)
    in div (created by Catalog)
    in Catalog (created by Context.Consumer)
    in Connect(Catalog) (created by component)
    in component (created by Context.Consumer)
    in Route (created by Router)
    in Switch (created by Router)
    in Router (created by Context.Consumer)
    in Connect(Router) (created by Context.Consumer)
    in withRouter(Connect(Router)) (created by withI18nextTranslation(withRouter(Connect(Router))))
    in withI18nextTranslation(withRouter(Connect(Router))) (created by Wrapper)
    in div (created by Wrapper)
    in Wrapper (created by Context.Consumer)
    in Connect(Wrapper) (created by Context.Consumer)
    in withRouter(Connect(Wrapper)) (created by withI18nextTranslation(withRouter(Connect(Wrapper))))
    in withI18nextTranslation(withRouter(Connect(Wrapper)))
    in Router (created by BrowserRouter)
    in BrowserRouter
    in Provider  
app.min.js:63615:7
Warning: Failed prop type: Invalid prop `selected` supplied to `Dropdown`.
    in Dropdown (created by withI18nextTranslation(Dropdown))
    in withI18nextTranslation(Dropdown) (created by CatalogGrid)
    in div (created by CatalogGrid)
    in section (created by CatalogGrid)
    in section (created by CatalogGrid)
    in CatalogGrid (created by withI18nextTranslation(CatalogGrid))
    in withI18nextTranslation(CatalogGrid) (created by Catalog)
    in main (created by Catalog)
    in div (created by Catalog)
    in Catalog (created by Context.Consumer)
    in Connect(Catalog) (created by component)
    in component (created by Context.Consumer)
    in Route (created by Router)
    in Switch (created by Router)
    in Router (created by Context.Consumer)
    in Connect(Router) (created by Context.Consumer)
    in withRouter(Connect(Router)) (created by withI18nextTranslation(withRouter(Connect(Router))))
    in withI18nextTranslation(withRouter(Connect(Router))) (created by Wrapper)
    in div (created by Wrapper)
    in Wrapper (created by Context.Consumer)
    in Connect(Wrapper) (created by Context.Consumer)
    in withRouter(Connect(Wrapper)) (created by withI18nextTranslation(withRouter(Connect(Wrapper))))
    in withI18nextTranslation(withRouter(Connect(Wrapper)))
    in Router (created by BrowserRouter)
    in BrowserRouter
    in Provider  
app.min.js:63615:7
SyntaxError: invalid regexp group  
app.min.js:1262:15
"The above error occurred in the <UserLocation> component:
    in UserLocation (created by Context.Consumer)
    in Connect(UserLocation) (created by Context.Consumer)
    in withRouter(Connect(UserLocation)) (created by withI18nextTranslation(withRouter(Connect(UserLocation))))
    in withI18nextTranslation(withRouter(Connect(UserLocation))) (created by Nav)
    in nav (created by Nav)
    in Nav (created by Context.Consumer)
    in Connect(Nav) (created by Context.Consumer)
    in withRouter(Connect(Nav)) (created by withI18nextTranslation(withRouter(Connect(Nav))))
    in withI18nextTranslation(withRouter(Connect(Nav))) (created by Wrapper)
    in section (created by Wrapper)
    in div (created by Wrapper)
    in Wrapper (created by Context.Consumer)
    in Connect(Wrapper) (created by Context.Consumer)
    in withRouter(Connect(Wrapper)) (created by withI18nextTranslation(withRouter(Connect(Wrapper))))
    in withI18nextTranslation(withRouter(Connect(Wrapper)))
    in Router (created by BrowserRouter)
    in BrowserRouter
    in Provider

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries."  
app.min.js:89437:5
"The above error occurred in the <UserLocation> component:
    in UserLocation (created by Context.Consumer)
    in Connect(UserLocation) (created by Context.Consumer)
    in withRouter(Connect(UserLocation)) (created by withI18nextTranslation(withRouter(Connect(UserLocation))))
    in withI18nextTranslation(withRouter(Connect(UserLocation))) (created by Header)
    in div (created by Header)
    in header (created by Header)
    in Header (created by Context.Consumer)
    in Connect(Header) (created by withI18nextTranslation(Connect(Header)))
    in withI18nextTranslation(Connect(Header)) (created by Context.Consumer)
    in withRouter(withI18nextTranslation(Connect(Header))) (created by Wrapper)
    in section (created by Wrapper)
    in div (created by Wrapper)
    in Wrapper (created by Context.Consumer)
    in Connect(Wrapper) (created by Context.Consumer)
    in withRouter(Connect(Wrapper)) (created by withI18nextTranslation(withRouter(Connect(Wrapper))))
    in withI18nextTranslation(withRouter(Connect(Wrapper)))
    in Router (created by BrowserRouter)
    in BrowserRouter
    in Provider

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries."  
app.min.js:89437:5
Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in UserLocationModal (created by UserLocation)
    in div (created by UserLocation)
    in UserLocation (created by Context.Consumer)
    in Connect(UserLocation) (created by Context.Consumer)
    in withRouter(Connect(UserLocation)) (created by withI18nextTranslation(withRouter(Connect(UserLocation))))
    in withI18nextTranslation(withRouter(Connect(UserLocation))) (created by Nav)
    in nav (created by Nav)
    in Nav (created by Context.Consumer)
    in Connect(Nav) (created by Context.Consumer)
    in withRouter(Connect(Nav)) (created by withI18nextTranslation(withRouter(Connect(Nav))))
    in withI18nextTranslation(withRouter(Connect(Nav))) (created by Wrapper)
    in section (created by Wrapper)
    in div (created by Wrapper)
    in Wrapper (created by Context.Consumer)
    in Connect(Wrapper) (created by Context.Consumer)
    in withRouter(Connect(Wrapper)) (created by withI18nextTranslation(withRouter(Connect(Wrapper))))
    in withI18nextTranslation(withRouter(Connect(Wrapper)))
    in Router (created by BrowserRouter)
    in BrowserRouter
    in Provider  
app.min.js:69998:5

Unread post by **Moonchild** » 2022-04-07, 11:38

Off-topic:

Indigoprophet wrote: ↑
2022-04-07, 10:08
Don't quibble over words

Words is all we have on a forum - the least you can do is be clear in what you write and use the right expressions.

Indigoprophet wrote: ↑
2022-04-07, 10:08
Are you serious? I provided some examples

You didn't provide anything useful. A screenshot of website content with an info bar that tells you (based on some arbitrary check) that they don't support Pale Moon because they think it's an old Firefox is nothing we can do anything with.

Indigoprophet wrote: ↑
2022-04-07, 10:08
it would explain the reason of this mess with different sites in one place

As already explained to you different sites may run into different issues. The web compatibility board is set up to (try and) provide solutions for people with specific websites, keeping things organized somewhat by keeping one thread per website.

Indigoprophet wrote: ↑
2022-04-07, 10:08
That's not an answer of a developer who cares for the quality of his product.

But that is and answer of a developer who actually wants to help the user with their problem that they cannot immediately solve themselves.

You have a choice of browsers. Your use of them should not frustrate you. If you can't use the web with Pale Moon without getting frustrated with it -- whether it be by arbitrary info bars that don't actually influence behaviour as part of the mainstream browsers to remain "supported better" even if no feature checking is performed, or actual content-by-js issues due to the fragile setup of frameworks -- then you should be using something more aligned with your browsing behaviour and the websites you tend to visit. That is a user-centric solution, not a "retain every user at all cost" solution. If Pale Moon is not useful for you, then don't use it. See also the statement on www.palemoon.org:

www.palemoon.org wrote:It is released "as-is" and in the hope that it will be useful to its users.

Lucio Chiappetti · Unread post by **Lucio Chiappetti** » 2022-04-07, 12:48

www.palemoon.org wrote:It is released "as-is" and in the hope that it will be useful to its users.

It certainly is, and is also one of the best, if not THE best, project in terms of responsivity of the developers to users' needs ! Thanks again !

davews · Unread post by **davews** » 2022-04-07, 15:47

I would have hoped after the recent episode this forum would be now a little less hostile, sadly not. For the record after finding Palemoon no longer working with reddit (use of old.reddit is not the answer) I have now moved over to Vivaldi. Much as I despise Chromium and would like to support Palemoon, I have to use a browser that works all the time. Vivaldi does, Palemoon does not and their forums are a much more pleasant experience.

Unread post by **moonbat** » 2022-04-08, 00:28

davews wrote: ↑
2022-04-07, 15:47
I would have hoped after the recent episode this forum would be now a little less hostile, sadly not.

Hostile? You have a user who can't be bothered to post either the fully required information, or in the correct subforum even when asked to do so and somehow it's everybody else's fault? Like I've asked before, what premium level tech support channel do you imagine you've been paying for to have this level of entitlement?

gepus · Unread post by **gepus** » 2022-04-08, 07:16

davews wrote: ↑
2022-04-07, 15:47
... and their forums are a much more pleasant experience.

Let's hope that henceforward you'll stick to that one. For ever!

Pallid Planetoid · Unread post by **Pallid Planetoid** » 2022-04-08, 07:46

Please.... personal animus is not at all useful.

Indigoprophet · Unread post by **Indigoprophet** » 2022-04-08, 08:34

In a single sentence, we've got lots of verbiage and frame-ups and silence on the heart of the matter. Quite revealing, my main questions remained unanswered:

Considering the name of that forum branch (Web Compatibility Support board), this pretext looks not only stupid, but also like an attempt to pipe me down. It that's the case, the question is why?

But how do you explain this issue for non-Chromium browsers?

The obvious truth is that a browser is useful only when it's working on all operational sites, otherwise it's useless. And you're saying that we must accept it.
But the saddest thing about this is that you're putting in jeopardy the future of a privacy-friendly product which is not a skank of big companies like Google. These products are worth its weight in gold these days, but with such attitude you're pushing your users away from it. The users who were willing to support it.

And yes, you are

hostile

.

Pale Moon forum

Important sites disfunctional on PaleMoon

Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon

Re: Important sites disfunctional on PaleMoon