9 Oct
2014
9 Oct
'14
11:15 a.m.
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
9 Oct
9 Oct
11:23 a.m.
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(a)yahoo.fr>fr>:
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
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
11:30 a.m.
On 9 Oct 2014 at 11:24:27, Guillaume Louis-Marie Delhumeau
(gdelhumeau@xwiki.com(mailto:gdelhumeau@xwiki.com)) wrote:
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
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
11:38 a.m.
On 9 Oct 2014 at 11:32:04, vincent(a)massol.net
(vincent@massol.net(mailto:vincent@massol.net)) wrote:
On 9 Oct 2014 at 11:24:27, Guillaume Louis-Marie Delhumeau
(gdelhumeau@xwiki.com(mailto:gdelhumeau@xwiki.com)) wrote:
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
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
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 
10 Oct
10 Oct
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
13 Oct
13 Oct
5:53 p.m.
On Fri, Oct 10, 2014 at 1:50 PM, Denis Gervalle <dgl(a)softec.lu> wrote:
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:
>
> > 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
Just FTR, the top menu in Colibri requires JavaScript.
>
>> @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.
> So,
> I think this has to be discussed and voted once for all.
>
>
>> Thanks
>> -Vincent
>
>> > 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
>
>
>
>
> --
> Denis Gervalle
> SOFTEC sa - CEO
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
9 Oct
9 Oct
12:06 p.m.
Ok thanks you for your answer.
... then I will be more carreful with my JavasciptExtensions :-))
________________________________
De : "Guillaume "Louis-Marie" Delhumeau"
<gdelhumeau(a)xwiki.com>
À : Pascal BASTIEN <pbasnews-xwiki(a)yahoo.fr>fr>; XWiki Developers
<devs(a)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(a)yahoo.fr>fr>:
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
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
3626
days inactive
3630
days old
6 comments
5 participants
participants (5)
-
Denis Gervalle -
Guillaume "Louis-Marie" Delhumeau -
Marius Dumitru Florea -
Pascal BASTIEN -
vincent＠massol.net