Discussion:
[xwiki-devs] improve flamingo menu?
Pascal BASTIEN
2014-10-09 09:15:38 UTC
Permalink
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
Guillaume "Louis-Marie" Delhumeau
2014-10-09 09:23:43 UTC
Permalink
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...

Thanks,
Post by 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
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Delhumeau (gdelhumeau-l2mTs9s+***@public.gmane.org)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
vincent@massol.net
2014-10-09 09:30:41 UTC
Permalink
 
Post by Guillaume "Louis-Marie" Delhumeau
Hello.
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
Post by Guillaume "Louis-Marie" Delhumeau
Thanks,
Post by 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
vincent@massol.net
2014-10-09 09:38:13 UTC
Permalink
Post by ***@massol.net
Post by Guillaume "Louis-Marie" Delhumeau
Hello.
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…
* 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?
Actually I think we haven’t fully concluded yet and we have some disagreement… :) I’ve found this brainstorming thread:
http://markmail.org/message/shnmkflkcqunwpmb

Thanks
-Vincent
Post by ***@massol.net
Thanks
-Vincent
Post by Guillaume "Louis-Marie" Delhumeau
Thanks,
Post by 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
http://lists.xwiki.org/mailman/listinfo/devs
Denis Gervalle
2014-10-10 10:50:50 UTC
Permalink
On 9 Oct 2014 at 11:24:27, Guillaume Louis-Marie Delhumeau (
Post by Guillaume "Louis-Marie" Delhumeau
Hello.
http://getbootstrap.com/components/#navbar
They are javascript-dependent, indeed. There is no plan to rewrite them
in
Post by Guillaume "Louis-Marie" Delhumeau
pure CSS, so yes, XWiki is not working anymore without JavaScript…
AFAIK our last position (which isn’t mentioned anywhere on xwiki.org BTW)
* 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?
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.
Thanks
-Vincent
Post by Guillaume "Louis-Marie" Delhumeau
Thanks,
Post by 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
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
Marius Dumitru Florea
2014-10-13 15:53:15 UTC
Permalink
Post by Denis Gervalle
On 9 Oct 2014 at 11:24:27, Guillaume Louis-Marie Delhumeau (
Post by Guillaume "Louis-Marie" Delhumeau
Hello.
http://getbootstrap.com/components/#navbar
They are javascript-dependent, indeed. There is no plan to rewrite them
in
Post by Guillaume "Louis-Marie" Delhumeau
pure CSS, so yes, XWiki is not working anymore without JavaScript…
AFAIK our last position (which isn’t mentioned anywhere on xwiki.org BTW)
* 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
Just FTR, the top menu in Colibri requires JavaScript.
Post by Denis Gervalle
@Devs: Is that correct?
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.
Yes. I'd rather spend time on exposing the full XWiki model through
URLs (improve our REST APIs). Someone that browses the web with
JavaScript disabled probably knows how to use wget.
Post by Denis Gervalle
So,
I think this has to be discussed and voted once for all.
Thanks
-Vincent
Post by Guillaume "Louis-Marie" Delhumeau
Thanks,
Post by 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
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
_______________________________________________
devs mailing list
http://lists.xwiki.org/mailman/listinfo/devs
Pascal BASTIEN
2014-10-09 10:06:05 UTC
Permalink
Ok thanks you for your answer.


... then I will be more carreful with my JavasciptExtensions :-))



________________________________
De : "Guillaume "Louis-Marie" Delhumeau" <gdelhumeau-l2mTs9s+***@public.gmane.org>
À : Pascal BASTIEN <pbasnews-xwiki-***@public.gmane.org>; XWiki Developers <***@xwiki.org>
Envoyé le : Jeudi 9 octobre 2014 11h23
Objet : Re: [xwiki-devs] improve flamingo menu?



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...

Thanks,





2014-10-09 11:15 GMT+02:00 Pascal BASTIEN <pbasnews-xwiki-***@public.gmane.org>:

Hello
Post by Pascal BASTIEN
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
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Delhumeau (gdelhumeau-l2mTs9s+***@public.gmane.org)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Loading...