Hi Francis, Since in the mobile world, smartphones are stuck with there OS version, I don't know if supporting only n-1 version is enougth. And I'm not sure if this kind of web responsive design will work well on low-end smartphones.
I'm aware there is already many JS in the V2, but it is more old-browser friendly. With the V3 I'm only able to login with my favorite web browser and nothing else. As I said I am aware that I have an old version but it's the first time I have this kind of problem. I didn't know about ARIA, but I am glad to discover this standard. If the V2 will continue to work, and will still be available in the repositories, it's fine for me, I'll continue with it, and with Thunderbird. But you asked for feedbacks, so I gave you mine :) Best regards > >> On Apr 3, 2015, at 10:29 AM, Francis Lachapelle <flachape...@inverse.ca> >> wrote: >> >>> I insist, but please, make the new interface with less JS than this >>> one. >>> Having everything made by scripts is a bad ideas. It's less accessible >>> (for disable people and for web browsers), and it's slower than the >>> HTML/CSS rendering. Think about old/low-end smartphones, and about >>> people >>> who doesn't have a Gecko/Blink web browser. >> >> The Web interface of SOGo has always required JavaScript and the amount >> of JavaScript code will certainly increased in v3. However, we will >> avoid any change to the database schema so it will be possible to run >> both v2 and v3 in parallel with the same data. > > One more thing: regarding accessibility, v3 will be better than v2 as we > will add ARIA attributes to our Web templates: > > http://www.w3.org/TR/wai-aria/ > https://docs.angularjs.org/api/ngAria > > > Francis-- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
