Core functionality should not be JavaScript dependent.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- fuzzy@fuzzynuts

fuzzy - 0 likes
- Jerome Bakker@jeabakker

Jerome Bakker - 0 likes
- fuzzy@fuzzynuts

fuzzy - 1 like
You must log in to post replies.Well, it's unfortunate nobody wants to discuss this topic. I'v fixed it before by over riding most of the default JS in my themes. It wasn't very difficult to fix, but it makes upgrading more difficult than it needs to be. It is a huge flaw in the core platform that deviates from very basic best practice standards.
If you have any suggestions on how to make core less dependent on JS, feel free to submit a Pull Request to Elgg https://github.com/Elgg/Elgg with your changes.
Why would depending on JS be a problem? If it's an accessibility issue, we try to make most of core work just fine.
Maybe you have other suggestions? Those are always welcome. Maybe the best suggestions could be reported https://github.com/Elgg/Elgg/issues
Hi Jerome,
For myself I always develop without JS first for accessibilty. then use Javascript as a feature, this ensures that no matter what the site will always function. The main case where this is an issue in elgg is comments, if you disable JS there is no way for users to comment, most other instances are in individual plugins where it can be corrected in the plugin, I do recal many years ago fixing this issue, but today that code is probably stale if I could even find it again. I posted this mostly to guage if there is support for a project like this. Accessibility is so often forgotten in modern web, but in this case it impeeds normal functionality. I'll keep checking if more support arives, other wise I'll just keep it on my when I get to it list. Thanks Jerome.