Re: [Dolibarr-dev] Proposal to remove $conf->global->MAIN_DISABLE_JAVASC
From:
Doursenaud , Raphaël
Subject:
Re: [Dolibarr-dev] Proposal to remove $conf->global->MAIN_DISABLE_JAVASCRIPT option in 3.8
Date:
Mon, 19 Jan 2015 16:06:06 +0100
Hi,
I'm Laurent's side here.
Ensuring our tool works properly even without _javascript_ is a premium.
It's very easy to forget these days with full JS apps that we need to have a proper HTML fallback that meets real use cases (text browser, slow connection/clients, accessibility…).
Keeping the separation explicit forces developers to think about it.
Of course accessibility is now doable with JS only but it's an awful lot of work when a simple HTML fallback does the job.
The selenium tests would be awesome but it's a lot of work ;)
About accessibility (blatant thread hijacking):
I don't know if we made a formal announcement but we attended a presentation with Charles Benke from Jean-Philippe Mengual at the latest RMLL about Dolibarr usability for blind people. (https://2014.rmll.info/conference223)