Wedge

Public area => The Pub => Features => Discussion démarrée par: Arantor le 14 Février 2012 à 02:31

Titre: Requiring JS in the admin panel
Posté par: Arantor le 14 Février 2012 à 02:31
I'm not sure if we talked about this or not, but I'm seriously debating enforcing JS to be present for the admin panel. While I can understand non-JS fallbacks for the normal forum, I'm less clear on it in the admin area, though I can see the argument in favour of accommodating screen readers etc. But even there I'm kind of thinking that it might be better to use JS primarily and not have the fallbacks, because I'm just thinking that there's no good way the admin panel can work for non-sighted users, there just isn't.

Thoughts?
Titre: Re: Requiring JS in the admin panel
Posté par: Norodo le 14 Février 2012 à 02:51
The only people who could have any sort of issue with this would be as you mentioned people using screen readers. Now I have no numbers on this, but in my head, people with screen readers do not seem like likely people to set up forams. Even if there is the odd one around, it depends on the javascript you are using and what the screen reader is capable of. Some of them can handle JS to some extent. And even if it can't, sometimes people can ask for help too. :)
 
TL;DR: Go for it.
Titre: Re: Requiring JS in the admin panel
Posté par: Nao le 14 Février 2012 à 07:11
I suppose blind admins will care little about the eye candy of Wedge anyway so I'd probably advise them to use SMF...
Titre: Re: Requiring JS in the admin panel
Posté par: live627 le 14 Février 2012 à 07:17
Wait, when was Wedge about the eye candy? :P
Titre: Re: Requiring JS in the admin panel
Posté par: Nao le 14 Février 2012 à 07:47
I'm eye candy to begin with!
Titre: Re: Requiring JS in the admin panel
Posté par: live627 le 14 Février 2012 à 08:21
* puts candy in eye "Ooh, eye candy, so purdy!"
* Tries to remove it "Oh it's sticky. And it hurts!"



...actually, I wonder if some dumb kid has done that.
Titre: Re: Requiring JS in the admin panel
Posté par: Arantor le 14 Février 2012 à 08:23
Probably in America, after all Ralph Wiggum had to be based on something...
Titre: Re: Requiring JS in the admin panel
Posté par: live627 le 14 Février 2012 à 08:27
lmao

Eddie: Sorry, Chief, we found Ralph with your candy.
Wiggum: I need to maintain my size 56!
Titre: Re: Requiring JS in the admin panel
Posté par: Nao le 14 Février 2012 à 08:36
Citation de Arantor le 14 Février 2012 à 08:23
Probably in America, after all Ralph Wiggum had to be based on something...
Like Moe is based on Rich Hall?
Titre: Re: Requiring JS in the admin panel
Posté par: Arantor le 14 Février 2012 à 08:47
Yup, something like that, but less about a specific person.
Titre: Re: Requiring JS in the admin panel
Posté par: Arantor le 26 Février 2012 à 18:15
Anyway, back on topic for a moment. There is now at least one area that specifically requires JavaScript in the ACP (moderation filters)

Should there be a nice warning at the top, obviously hidden for JS users, indicating that things may not work properly or at all in the ACP for non JS users?
Titre: Re: Requiring JS in the admin panel
Posté par: Dr. Deejay le 26 Février 2012 à 18:30
Citation
Should there be a nice warning at the top, obviously hidden for JS users, indicating that things may not work properly or at all in the ACP for non JS users?
Aye, definitely
Titre: Re: Requiring JS in the admin panel
Posté par: Nao le 26 Février 2012 à 20:16
I don't know. Are there that many people not using JS? And among them -- how many are technical-minded?
Titre: Re: Requiring JS in the admin panel
Posté par: Arantor le 26 Février 2012 à 20:20
I don't think it's *that* important but I figured I show ask. We did it in SimpleDesk, but we did it throughout SD rather than just the admin area.
Titre: Re: Requiring JS in the admin panel
Posté par: Norodo le 26 Février 2012 à 20:21
It seems like a small effort with few drawbacks, so I can't see why not.
Titre: Re: Requiring JS in the admin panel
Posté par: Arantor le 10 Mars 2012 à 13:27
OK, I'll add this in a bit (hopefully later today depending on how things work out). My plan of action is to do as I did in SimpleDesk, create a new template block with the <noscript> message (and an icon, just for the sake of nicety) and inject it into the skeleton above all the content.