100% no-JS clients compatibility
-
@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.
-
Maybe a stupid reflexion but since NodeJS is based uppon JS if you disable JavaScript that's logic that the forum doesn't work as expected. And more over all the realtime with sockets won't be avaible too, same for the ajax navigation I don't really see how NodeBB could be noJS.
-
What features of the forum should be available without Javascript?
For instance:
- 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.
The solution seems pretty simple, use or allow javascript, or the forum is read only.
-
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
-
@psychobunny said:
I'm sorry, I can't click that link. I blocked vBulletin at router level years ago.
-
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.