> It is entirely possible for all of that to be true and for smacktoward's suspicion — that Moonchild's primary problem with Web Components is that they work poorly in Pale Moon and it would be a lot of trouble to fix that — to be true.
It is not true
for the simple fact that the next milestone release (v29) of pale moon will support WebComponents
> Neither of those really even contradict what smacktoward said, much less disprove it.
smacktoward repeats the same tired oversimplifications that PM is just "rebased itself on mainline Firefox circa Firefox 52" both my links prove that the above statement is fundamentally wrong.
It is not true
for the simple fact that the next milestone release (v29) of pale moon will support WebComponents
> Neither of those really even contradict what smacktoward said, much less disprove it.
smacktoward repeats the same tired oversimplifications that PM is just "rebased itself on mainline Firefox circa Firefox 52" both my links prove that the above statement is fundamentally wrong.