On 19/03/2021 14:12, Jonathan N. Little wrote:
Dirk Fieldhouse wrote:
...> >> Off-topic: shouldn't that extension be built into SM for all sites?
No, SM should be upgraded, but because of its legacy framework not only
will upgrade break extension support but require a major rewrite of the
codebase. A lot to ask of the volunteer developers.
...
Generally, what has changed since Firefox and SeaMonkey were in
lock-step is new or changed JS APIs, in particular so-called Web Components.
As this (classic) extension has done the job of implementing the subset
of these APIs expected by GitHub (that they couldn't be bothered to send
polyfills for), maybe it provides a good route to doing that for other
sites, at least until SM gets native support for them.
I wonder if there is anything specific to GH in the extension other than
(I assume) that it enables the WC APIs for GH only, and the selected
subset of APIs?
/df
--
London
UK
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
