Pale Moon forum

Since Google has made HTML 5 and Javascript support a permanently moving target, how do you decide what or when to add support for in Pale Moon?

This has beem discussed already badnic--I mean moonbat.

New Tobin Paradigm wrote: ↑

2019-12-07, 10:44

This has beem discussed already badnic--I mean moonbat.

why bad nick?

Badnick had a habit of creating dozens of bullshit question threads about topics that have already been discussed on this forum.

You are doing the same thing. Please stop.

moonbat wrote: ↑

2019-12-07, 10:34

when to add support for in Pale Moon?

Like so many other things in life, also this depends of development time available/complexity relation.

Also, certain things can be implemented by a developer, and as Open Source offers also the option that users can and should contribute, certain features will come only if implemented by us users

Also, that features which can be implemented by users - are bounty material. So - you want to try on your own, or you know skilled people in your circle of friends or from work or elsewhere which would be interested to help Open Source projects... This here is a good place to start and contribute

https://github.com/MoonchildProductions ... l%3ABounty

It also depends if it is actually being used in the wild.

Why is this thread a thing?
See: https://www.palemoon.org/roadmap.shtml under "Core work"

Well, I could be mistaken, but I believe Mozilla or Netscape at one point had to implement various nonstandard Internet Explorer features because they were so widely used in order to improve compatibility. I think that's all you can do with a living standard. Come up with an implementation that works for the features UXP users actually need and use, avoid the features that would compromise user security as much as possible, and just keep going one day at a time.

Without an established standard that evolves in a predictable way over time, it just means we can't point to any kind of reference specification as a reason why websites shouldn't do something, and will just be forced to adapt to whatever they are doing in the process of targeting Chrome. That is honestly how the web really works anyway and always has, everyone basically just stopped pretending that standards matter because Chrome is dominant enough now that the pretense of having a standard is no longer necessary. There were a few years when IE, Chrome, and Firefox were all competing hard and thus coordinating on a standard was essential, but that's no longer the world we live in and so standards are falling by the wayside. Web developers are not only not upset about this, most of them are pleased and actively admit they seek to "reduce fragmentation."

I mean, if you think about it, the meaning of this situation is perfectly obvious. A living standard means we can't plan ahead as much. We basically have to react to what Google implements and how quickly webmasters start using those features after the fact. Which is rather unfortunate, but it isn't the end of the world. It would be like trying to keep up with the English language if they stopped publishing dictionaries and teaching grammar in school. We would still be able to understand each other, but we'd have to work a lot harder at keeping up with colloquialisms and changes in grammar organically due to lack of a reference standard to slow down and help coordinate change.

adesh wrote: ↑

2019-12-08, 09:44

Living one day at a time.

That's probably also because of the current society where one's job is apparently as fleeting as the wind. Do you want to be planning long-term if you don't even know you'd still be employed there? Not to mention the necessary short-term-only approaches required for being outsourced. So it may not be a choice, but rather a circumstance.