Pale Moon no longer supported at Github.com since 28.16.0?
Moderator: trava90
Forum rules
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.
Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.
Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
- Clear any current output
- Navigate or refresh the page in question
- Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
Pale Moon no longer supported at Github.com since 28.16.0?
I updated to Pale Moon 28.16.0 (x64) for Windows earlier today and subsequently visited Github.com to provide follow-up feedback on a Pale Moon extension hosted there. For the first time, I got a message that my browser was not supported, and the message-box buttons no longer worked. (I'm using the native user agent, which I gather was the previous "workaround" for Github to continue working in Pale Moon.) Can Github compatibility once again be jury-rigged on your end? Thanks very much for looking into this. All the best.
-
- Moon Magic practitioner
- Posts: 2408
- Joined: 2018-05-05, 13:29
Re: Pale Moon no longer supported at Github.com since 28.16.0?
Microsoft (and thus GitHub) gave up to Google's dictatorship of the web and so it started using technologies that as of now work only on Chrome, Chrome-alikes and Chrome derivates and there no real workarounds.
The Pale Moon and UXP teams are working on it, but it's a long process to implement Google's garbage.
The Pale Moon and UXP teams are working on it, but it's a long process to implement Google's garbage.
-
- Fanatic
- Posts: 121
- Joined: 2018-01-22, 23:04
Re: Pale Moon no longer supported at Github.com since 28.16.0?
It works in Firefox 82, so it is not yet exclusively limited to the Chrome-alikes.
-
- Moon Magic practitioner
- Posts: 2985
- Joined: 2015-09-26, 04:51
- Location: U.S.
Re: Pale Moon no longer supported at Github.com since 28.16.0?
Not a fix, but there is an extension that helps: Github Web Components Polyfill (first mentioned here).
FYI, given GitHub's lack of support, the project's repositories were moved from GitHub to a Gitea instance.
See threads here and here.
Re: Pale Moon no longer supported at Github.com since 28.16.0?
It's beyond me why Google/Alphabet's de facto usurpation of the W3C's role in setting Web standards and protocols isn't a leading focus of antitrust probes. (Well ... at least in the EU, where regulators, politicians, and judges are still subject to some semblance of conflict-of-interest and anti-corruption rules. In the US, antitrust authorities are already fully captured.) To my mind, it's a more fundamental threat than Google's search dominance, advertising "monopoly," or promotion of its own services. Only Facebook rivals Google in the volume and breadth of kompromat they have on Internet users (including regulators, pols, and judges), so I'm thinking ... blackmail? All speculation aside, effectively handing control of how the Web works over to Google/Alphabet promises a very dystopian future for the Internet.vannilla wrote: ↑2020-11-24, 23:30Microsoft (and thus GitHub) gave up to Google's dictatorship of the web and so it started using technologies that as of now work only on Chrome, Chrome-alikes and Chrome derivates and there no real workarounds.
The Pale Moon and UXP teams are working on it, but it's a long process to implement Google's garbage.
Re: Pale Moon no longer supported at Github.com since 28.16.0?
The answer is simple.. Actually understanding the simple answer requires complicated backstory of a bunch of events and history but the concluding answer is simple. I'm not even going to go into it though until certain things are settled.
Regardless, see my previous posts and those of others on this subject.
Regardless, see my previous posts and those of others on this subject.
Re: Pale Moon no longer supported at Github.com since 28.16.0?
coffeebreak wrote: ↑2020-11-25, 01:08
Not a fix, but there is an extension that helps: Github Web Components Polyfill (first mentioned here).
FYI, given GitHub's lack of support, the project's repositories were moved from GitHub to a Gitea instance.
See threads here and here.
Thanks for the tip on github-wc-polyfill. I don't have the technical chops to understand how filling my water closet with polyester will help, but if it makes Github work better, I'm going to install the extension.

Thanks also for bringing the Gitea move to my attention. I actually filed my initial issue report on Github back in August, before the Gitea move happened, so it looks like I might have a real excuse this time!
I really appreciated your reply. It's sometimes hard to keep up...
-
- Knows the dark side
- Posts: 5592
- Joined: 2015-12-09, 15:45
Re: Pale Moon no longer supported at Github.com since 28.16.0?
It also doesn't help that politicians and legislators are far more clueless about tech than even the general public. They don't understand the issues involved with the advertising/search aspects, let alone what W3C is meant for and how it's been subverted.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

KDE Neon on a Slimbook Excalibur (Ryzen 7 8845HS, 64 GB RAM)
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Jabber: moonbat@hot-chili.net

KDE Neon on a Slimbook Excalibur (Ryzen 7 8845HS, 64 GB RAM)
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Jabber: moonbat@hot-chili.net
-
- Moonbather
- Posts: 67
- Joined: 2016-01-27, 02:09
Re: Pale Moon no longer supported at Github.com since 28.16.0?
Has anyone with a stance (such as Moonchild productions) tried contacting the EU antitrust office about this? I suspect they don't look at issues until they are reported.[PCMartin] wrote: ↑2020-11-25, 16:32It's beyond me why Google/Alphabet's de facto usurpation of the W3C's role in setting Web standards and protocols isn't a leading focus of antitrust probes. (Well ... at least in the EU, where regulators, politicians, and judges are still subject to some semblance of conflict-of-interest and anti-corruption rules. In the US, antitrust authorities are already fully captured.) To my mind, it's a more fundamental threat than Google's search dominance, advertising "monopoly," or promotion of its own services. Only Facebook rivals Google in the volume and breadth of kompromat they have on Internet users (including regulators, pols, and judges), so I'm thinking ... blackmail? All speculation aside, effectively handing control of how the Web works over to Google/Alphabet promises a very dystopian future for the Internet.vannilla wrote: ↑2020-11-24, 23:30Microsoft (and thus GitHub) gave up to Google's dictatorship of the web and so it started using technologies that as of now work only on Chrome, Chrome-alikes and Chrome derivates and there no real workarounds.
The Pale Moon and UXP teams are working on it, but it's a long process to implement Google's garbage.
Re: Pale Moon no longer supported at Github.com since 28.16.0?
Fuck the EU.. the MOST they ever have done is fined Microsoft an amount of money that is a slap on the wrist to them. Besides, them and their barely elected to completely un-elected bureaucratic rabble have more important shit to do.. Like world domination and Microsoft is apart of that plan. Not as much as Google or Facebook mind you but still apart.
-
- Astronaut
- Posts: 670
- Joined: 2017-03-23, 19:56
Re: Pale Moon no longer supported at Github.com since 28.16.0?
You don't know what you're talking about The EU has become the new eUSSR for several years.
https://www.gatestoneinstitute.org/8189 ... censorship
https://www.politico.eu/article/google- ... terrorist/
https://slate.com/technology/2019/10/eu ... rship.html
Windows 10 pro /64 (version 1809)
PM last/64
PM last/64
Re: Pale Moon no longer supported at Github.com since 28.16.0?
I am not sure how I feel about you agreeing with me. Oh well, I'll just chalk it up to 2020.
-
- Astronaut
- Posts: 670
- Joined: 2017-03-23, 19:56
Re: Pale Moon no longer supported at Github.com since 28.16.0?
Because are different subjects. Is not about agreeing or not with you , is about truth.
Windows 10 pro /64 (version 1809)
PM last/64
PM last/64
-
- Moon lover
- Posts: 91
- Joined: 2019-05-25, 23:40
Re: Pale Moon no longer supported at Github.com since 28.16.0?
I don't have any notifications regarding browser support on GitHub, but I do have an issue where it fails to display information entirely (see screenshot). It's super annoying and things like these happen more and more with Pale Moon.
You do not have the required permissions to view the files attached to this post.
-
- Moon Magic practitioner
- Posts: 2985
- Joined: 2015-09-26, 04:51
- Location: U.S.
Re: Pale Moon no longer supported at Github.com since 28.16.0?
See the 4th post from the top in this thread for a workaround.
-
- Fanatic
- Posts: 198
- Joined: 2014-06-22, 22:23
- Location: Europe
Re: Pale Moon no longer supported at Github.com since 28.16.0?
Yesterday I logged into Github to comment using Linux PM 28.16.0 and got the info my browser being no longer supported. I still could log in, and also comment, but none of the markup like [[size=1] [/size]code[size=1] [/size]] or [[size=1] [/size]bold[size=1] [/size]] would work.
Then I switched to 28.17.0 and logged in today to reply again. This time I did not see the "your browser is not supported" info (maybe I only missed it, though), but still none of the markup is working.
I could still reply, but only using plain text, like with 28.16.0: no [[size=1] [/size]code[size=1] [/size]], no [[size=1] [/size]bold[size=1] [/size]], no [size=1] [/size][italic[size=1] [/size]], not any other markup works. (JavaScript is sure allowed)
Then I switched to 28.17.0 and logged in today to reply again. This time I did not see the "your browser is not supported" info (maybe I only missed it, though), but still none of the markup is working.
I could still reply, but only using plain text, like with 28.16.0: no [[size=1] [/size]code[size=1] [/size]], no [[size=1] [/size]bold[size=1] [/size]], no [size=1] [/size][italic[size=1] [/size]], not any other markup works. (JavaScript is sure allowed)
yours truly, Rava
-
- Moon Magic practitioner
- Posts: 2985
- Joined: 2015-09-26, 04:51
- Location: U.S.