dvdgmlwsk wrote:So, I'll just stay with Pale Moon 27 for now rather than fumble around with the shortcomings of Pale Moon 28.
Considering the shortcomings in this case are the shortcomings of an extension (which isn't our code), then the "for now" in your sentence will be "as long as the extension developer doesn't update the extension". Unfortunately that can take a long time, and Pale Moon 27 actually has real shortcomings that v28 solves.
In general, I understand the desire to roll back by users because it's the easiest way to get short-term solutions (as in, it doesn't take any effort). But the resulting situation won't be viable long-term. For that solutions have to be found. People rolling back won't help finding those solutions (whether they are updated extensions, workarounds or enhancements to the browser core) and if everyone who happens to use the same extension you do has the same attitude of just wanting a silver platter, 5 second "make it work" solution, then nothing will ever happen to actually resolve compatibility and it becomes a dead-end street.