7 Jan
2014
7 Jan
'14
3:39 p.m.
In my point of view, we need to consider the cost of maintaining a
non-javascript version of all our features, in a period where we want more
interactivity (using jQuery or Angular for example).
Having a modern UI could be a great plus to have more users. About the
screen readers, I have heard that a lot of progress have been made and that
they can handle javascript now, but I need to read more about that.
2014/1/7 vincent(a)massol.net <vincent(a)massol.net>
+1 to officially drop support for
non-javascript-enable clients (browsers).
Ideally it shouldn’t show an error (not even sure we need to go to that
level) but the feature is allowed to not be present when javascript is not
enabled.
Thanks
-Vincent
On 7 Jan 2014 at 15:29:04, Guillaume Louis-Marie Delhumeau (
gdelhumeau(a)xwiki.com) wrote:
Hi devs,
In a recent pull request
(https://github.com/xwiki/xwiki-platform/pull/254), I have "fixed" a
bug reported by the accessibility validator by hiding a
link if javascript is not enabled on the browser. It didn't fix the fact
that the feature is unavailable without javascript, but at least the link
was not there.
I did it because I have the feeling that some committers think we don't
need support the navigation without javascript in 2014.
Now, it seems that we do not all agree about this.
That is why I think we should talk about this to decide what rule we should
put in place for the next years.
Thanks, in advance, for your opinions.
Louis-Marie
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs