Hi,
FYI, there already exist an issue [1] in Jira for the problem you have
mentioned, if I have properly understood. I`ve created the issue because I
did not have the time, at that moment, to do it.
Regarding the discussion, I`m -1 for explicitly writing code that checks
the presence of JavaScript (or HTML moved to JavaScript just so that it
gets added only when JS is activated, like your fix proposes).
If we decide to stop supporting non-JS UIs then that is that. The UI
elements will be there (links, menus, etc) but they will just not function
properly. That's what everybody does and, if we do go that way, I believe
it's a reasonable behavior. The web application (almost all by now)
*requires* that you have JS on (which is on by default) and that if you
feel like disabling it (because you probably know what you are doing) will
most likely know how to re-enable it and to detect problems caused by your
actions.
I too feel like the effort we are putting into non-js UIs is considerable
and I am not sure how appreciated or used it is by our users. Also, if
enterprise is our concern, then I doubt enterprise users will start
fiddling with the browser`s settings and start disabling JavaScript because
they are feeling naughty :) Also, Firefox started hiding the option to
disable JavaScript a while ago.
It may be a bit of a developer's pride for us to see the product run
without JS, but I`m not sure it`s ultimately very productive or gratifying
even.
+1 for dropping the backwards support, but only after we look into it a
bit, see what solutions exist for problematic users and maybe provide some
written guidelines on how to do it right.
Thanks,
Eduard
----------
[1]
http://jira.xwiki.org/browse/XWIKI-7970
On Tue, Jan 7, 2014 at 4:47 PM, Guillaume "Louis-Marie" Delhumeau <
gdelhumeau(a)xwiki.com> wrote:
For information, we have some some key features that
can not work without
JS right now:
- livetable
- the top menu bar
and maybe more...
So if we decide to enable non-javascript navigation, it means we must also
write non-javascript version of these features to be consistent.
2014/1/7 Caleb James DeLisle <cjd(a)hyperboria.ca>
+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:
+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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs