PM 28.14.2 Github

For support with specific websites

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:
  1. Clear any current output
  2. Navigate or refresh the page in question
  3. Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
New Tobin Paradigm

Re: PM 28.14.2 Github

Unread post by New Tobin Paradigm » 2021-02-14, 03:58

SlySven wrote:
2021-02-13, 22:23
As you suspected it was just me... :oops:
It happens.

BenFenner
Astronaut
Astronaut
Posts: 588
Joined: 2015-06-01, 12:52
Location: US Southeast

Re: PM 28.14.2 Github

Unread post by BenFenner » 2021-02-18, 17:04

JustOff wrote:
2020-10-15, 15:25
Here is a workaround: GitHub Web Components Polyfill.
Thank you for developing this extension! I found out about it today, and I believe I can now avoid other browsers in my day-to-day employment. :D

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35477
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: PM 28.14.2 Github

Unread post by Moonchild » 2021-02-18, 21:17

For now.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

coffeebreak
Moon Magic practitioner
Moon Magic practitioner
Posts: 2986
Joined: 2015-09-26, 04:51
Location: U.S.

Re: PM 28.14.2 Github

Unread post by coffeebreak » 2021-02-18, 23:07

Only if at some point GitHub implements a change that somehow cannot be addressed. Should that happen, it will be obvious to us all (and no point in speculating).

But that aside, there is no reason to believe the extension would stop working.
As shown in the change log, it's updated to keep it effective.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35477
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: PM 28.14.2 Github

Unread post by Moonchild » 2021-02-19, 00:26

For now, it is a workaround. A polyfill won't be able to fill in the blanks for all parts of the spec forever because it ultimately redefines how the web is structured and how content is delivered.
It can break at any time, is all I'm saying. it's not a solution, but the real solutions are currently out of reach, primarily due to something Github won't do because they consider Google WebComponents "part of a diverse and healthy set of modern web standards" and "{they} will continue to make use of them. For browsers that opt not to support these specifications, further degradation is a likelihood. It's not a goal of ours, by any means, but it is a likelihood."
Those are literal quotes from Github developer support (after they left me hanging for over 2 weeks).
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

BenFenner
Astronaut
Astronaut
Posts: 588
Joined: 2015-06-01, 12:52
Location: US Southeast

Re: PM 28.14.2 Github

Unread post by BenFenner » 2021-02-19, 03:16

Moonchild wrote:
2021-02-18, 21:17
For now.
Yes, of course.
I'll take it for now, and maybe steer my employer to a more friendly solution if/when I get the chance to sway them.
I take it Gitea could be decent choice?

Locked