10 Oct
2014
10 Oct
'14
12:50 p.m.
On Thu, Oct 9, 2014 at 11:30 AM, vincent(a)massol.net <vincent(a)massol.net>
wrote:
On 9 Oct 2014 at 11:24:27, Guillaume Louis-Marie Delhumeau (
gdelhumeau@xwiki.com(mailto:gdelhumeau@xwiki.com)) wrote:
This was also my understanding, however, by choosing Bootstrap, we have
clearly choose the Javascript way, since bootstrap does not gracefully
fallback. If we need to support such noscript issues, we will have to write
our own fallback, which may cost a lot of time for almost an edge case. So,
I think this has to be discussed and voted once for all.
Hello.
The top menu is actually written using the bootstrap components:
http://getbootstrap.com/components/#navbar
They are javascript-dependent, indeed. There is no plan to rewrite them
in
pure CSS, so yes, XWiki is not working anymore
without JavaScript…
AFAIK our last position (which isn’t mentioned anywhere on xwiki.org BTW)
was the following:
* Main features of XWiki should work without javascript
* Advanced features can require JS to be turned on
* Ideally nothing really awful should happen when JS is turned off
(graceful degradation)
* Flamingo requires javascript but if someone really insists on having
XWiki working without Javascript, they should use a skin not requiring
javascript such as Colibri
@Devs: Is that correct?
Thanks
-Vincent
--
Denis Gervalle
SOFTEC sa - CEO
Thanks,
2014-10-09 11:15 GMT+02:00 Pascal BASTIEN :
> Hello
>
> If javascript on browser is disabled or (a javascript function crashed)
> flamingo menus is not expandable anymore...
>
> It is possible to write a expandable/collapsed menu in pure CSS(without
> javascript) to avoid that.
>
> WDYT?
> Perhaps you already think about that... Menu in pure CSS will generate
> more problems?
>
>
> Pascal B
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs