Wedge
Public area => Bug reports => The Pub => Archived fixes => Topic started by: Auk on August 19th, 2013, 03:38 AM
-
Yup, can't create new topic :S
While on the subject, should we bother caring for users with javascript disabled? Fair enough the options seems a bit buried in Chrome and now Firefox... Opera is a bit easier to get to.
Edit: Ah, evidently, y'all really do care. :)
-
Given how much other stuff doesn't work already when trying to browse without JS...
Sure, we can add a warning easily enough. I'm most intrigued as to why the above occurs... for anyone wondering, the selectboxes are still hidden as they should be (because the custom selectboxes aren't then loaded) and they contain crazy-long content which pushes the subject box off the page even though it's otherwise visible.
-
Is it even worth 'fixing'..? :^^;:
-
It's not, as such, provided we add a warning that things just won't work properly with JavaScript disabled. Then we can safely ignore it entirely.
-
Any <noscript> tag will still add 50+ bytes to ALL pages just for that message, at least.
I'm not thrilled with the idea.
Firefox recently removed the ability to disable JS, Chrome doesn't have it, and IE, I can't remember, I think it's hidden in an obscure setting in the security area, so it's unlikely people would disable it, I guess...
-
Really? In my newest version of chrome, I can just go to advanced settings, click on the content button and a radio button for Javascript is right there. In IE 10, you can disable it, it's not labeled as Javascript though (Scripting, Active scripting.)
Edit:
Okay. How about this: Plugin for those who cares!!(http://wedge.org/pub/8244/make-obvious-to-users-that-their-javascript-is-disabled/) :D
-
I'll agree with the Chrome thing, it's how I investigated what was going on... And for the FF camp don't forget NoScript...
Hang on and I'll write such a plugin.
One thing I will say, I've thought about adding this before, multiple times, but always stopped because of the number of bytes it'll use.