This is not for tech support! Please do not post tech support questions in the "Development" board!Please make sure not to use this board for support questions. Most "bug reports" do not belong in this board and should initially be posted in Community Support or other relevant support boards.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.

As the sole champion of Pale Moon at my web development shop, it has fallen on me to make this thread.

We just spent some time debugging odd JS behavior on one of our sites (they are very light on JS as a general rule) which only Pale Moon exhibits (tested working in Opera, FF, IE, Chromium, Chrome, Safari, and Edge). We narrowed it down to the seeming lack of support for the ES6 `class` keyword in Pale Moon.I found this thread on the topic: viewtopic.php?f=13&t=14589&hilit=es6+class

I would have bumped that thread from January 2017, but it is locked. With all due respect, it seems to be 11 months since the last mention of this on the forum and the locked thread leaves tons of unanswered questions about the future of this feature. I'm not entirely sure what to expect with this as PM progresses. Is support not planned, ever? Or are we as forum members just not allowed to discuss it? Or what?

Either way, I'd like to see what the current state of things are in this area. We may have a work-around for our specific issue now, but I'd like to keep myself informed about the state of this feature in Pale Moon (hence this thread).I realize support for this may be very difficult. I'm just wondering if there is a vague plan to eventually support this? Or a solid plan to eventually support this? Or is support ever to be expected? With this information, I can make better educated plans for our shop's future. Thank you.

Last edited by BenFenner on Tue, 05 Dec 2017, 15:13, edited 1 time in total.

To be clear, our shop is not trying to use "class" in JavaScript. We are merely making use of a 3rd party plug-in that relies on it. We may find alternatives. JavaScript we write ourselves is not the problem.I may go make a bug report for this 3rd party plug-in.

Last edited by BenFenner on Tue, 05 Dec 2017, 14:57, edited 1 time in total.

As regards locked threads: all threads on this forum are automatically locked after a specific period of inactivity (more than half a year since the last activity) to prevent necro-posting on long-closed and concluded discussion topics that has been an constant issue lately. Don't take this kind of lock as a dismissal of the topic.

Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne

I've done some more work on getting the dependencies in (e.g. "super") but the more I see about how this all hooks together, the more ES6 classes are plainly a BAD IDEA, especially how it is all specced.With classes you're going to generate a very fragile dependency chain that works in a way completely a-typical to the way JavaScript normally works. I really don't think the little bit of convenience it creates for people wanting to do C++ abstraction comes anywhere near being proportional to the cost for the language as a whole.Classes in JS are simply a really, really bad idea, trying to enforce OO structures from a different language to something that is simply not designed to do things that way.

There's also no reason to use classes per se, as anything done with classes can be done with basic and completely compatible use of JS prototypes. Prototyping is there for a reason; use it.

Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne