100% no-JS clients compatibility
But you have to.
So yeah, that's a feature request. Please make NodeBB 100% usable (without the cool stuff JS offers, but with what shouldn't require JS).
Specifically for NodeBB, it functions as you correctly discovered, in read-only mode. We periodically check that NodeBB is browsable in read-only mode, though it's been awhile since we last checked.
As much as I hate to say it, for the aforementioned reasons, bringing NodeBB to 100% feature parity for a NoScript user would introduce a significant overhead that we cannot commit to supporting.
Sadly, the same can be said for our less represented users: IE users, users on slower smartphones, 2G networks, etc.
Sadly, the same can be said for our less represented users: IE users
They deserve it.
arasbm last edited by
I 100% agree with @julian's position here and also appreciate that the team is recognizing the need for making the forum as accessible as possible. But like any software project you have limited resources and have to pick your battle carefully.
I don’t mean to steal the original topic, but a related issue here is supporting email replies. If people can reply from email, they don’t even have to open the browser. I think that would helps cover most of, if not all, the people who would otherwise try to use a browser with JS disabled, or use some crippled browsers.
@a_5mith I should clarify, I mean IE8 and below XD We do support newer versions, and will resolve bug reports targeting recent versions.
@arasbm Reply-by-email is definitely doable with the emailer plugins, although the specific implementation may be different based on the provider. It's on my mind of things to do, although I'm always sidetracked these days with other features
Shard last edited by
Guest last edited by
It's on my mind of things to do, although I'm always sidetracked these days with other features
fixing all of the messes that @Ted and @a_5mith create when they get together.
The email replies, and probably the digests too, should be implemented as official plugin(s), IMO.
@pitaj digests? Digests are in core
@julian exactly. They should probably be reduced to an official plugin. And if they can't, add hooks to do so.
Digests are, IMO, a plugin kind of issue.
If they were a plugin, they could be implemented in different, custom, ways and stuff.
@pitaj Very good point The digests were added when the plugin system was in its infancy, so breaking it out into its own plugin is the correct thing to do
I understand the reasons, that just prevents any reasonably big community from choosing NodeBB. Maybe it shouldn't be a priority, but in my opinion it's something you can't release a v1.0 without.
esiao last edited by
@esiao Rewrite it in php...
Don't send me to the gallows... I'm sorry.
- Logging in
- Viewing posts
- Making posts
- Editing posts
- Deleting posts
- Previewing posts
I'm not seeing much point us debating what should and shouldn't be available without the use of JS. As JS is a requirement of websockets, which is (as Julian mentioned) the majority of the forum platform.
Yeah one thing we love a lot about node.js is the fact that we can share libraries across server and client side. So we only have to write certain modules once (form validation, for example) and distribute to both server and client side.
I think the read-only mode is a pretty good enough compromise though. For reference, both Facebook and Twitter put you in read-only mode as well. Some software don't even bother with this... just gives you a blank page
At least in read-only we do retain SEO value on some search engines that don't support JS yet, and of course we do display a message asking the user to switch on JS or download a newer browser
I'm sorry, I can't click that link. I blocked vBulletin at router level years ago.
@pitaj What you listed seems to be enough. Basic usability would be nice.
I'll never use NodeBB without JS enabled myself, I just wanted to point out that it's something required if you want to ease some big communities' choice
If you really need this functionality, you could start working on it yourself, and then I'm sure the devs would be glad to merge it into their code.