You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quite a few people nowadays run their browsers full-time with plugins which block all JavaScript to disable tracking scripts (like NoScript).
Not surprisingly this breaks half of openSNP's functionality if you don't whitelist the page. I believe it would be nice to have a graceful fallback to a clunkier interface if a user doesn't support JavaScript. It's something bigger to fix, you'd have to partially reimplement a few pages (replace a drop-down menu with all options, for example). If you don't agree, feel free to close this issue.
It's quite a lot of work, though. Much more than having everyone who blocks JavaScript, collectively whitelist openSNP, I'd assume. ;) On the other hand, it would benefit users of screen readers as well. And it would be a great opportunity to clean up the HTML...
I think Bootstrap does try to fall back to a HTML interface in case it cannot render a feature. In any case, we can always display a message saying OpenSNP works best with Javascript enabled, currently viewing in reduced functionality mode.
Quite a few people nowadays run their browsers full-time with plugins which block all JavaScript to disable tracking scripts (like NoScript).
Not surprisingly this breaks half of openSNP's functionality if you don't whitelist the page. I believe it would be nice to have a graceful fallback to a clunkier interface if a user doesn't support JavaScript. It's something bigger to fix, you'd have to partially reimplement a few pages (replace a drop-down menu with all options, for example). If you don't agree, feel free to close this issue.
Other "big" places like GitHub or Twitter don't do it, Twitter simply doesn't work without JavaScript. DuckDuckGo has a non-JS html fallback: https://duckduckgo.com/html/?q=bootstrap%20without%20jquery
The text was updated successfully, but these errors were encountered: