7 Jan
2014
7 Jan
'14
3:45 p.m.
I would say it's a case by case decision (we may want to keep critical
thing like editing a page/objects/class usable without javascript)
with the default being to consider working without javascript an
improvement and not a requirement.
On Tue, Jan 7, 2014 at 3:41 PM, Caleb James DeLisle <cjd(a)hyperboria.ca> wrote:
+1
Of course we always have to move cautiously and remember that DOM structure,
even if js generated, can be very important to vision impaired users.
Thanks,
Caleb
On 01/07/2014 03:30 PM, vincent(a)massol.net wrote:
--
Thomas Mortagne
+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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs