ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Make the layout usable without activated Javascript (Feature #660)

Added by Holger Just at 2011-10-13 08:20 pm. Updated at 2011-10-13 11:53 pm.

Status:Open Start date:2011-10-13
Priority:Normal Due date:
Assignee:- % Done:


Category:User interface
Target version:-
Remote issue URL: Affected version:


The basic layout and all important functions should be usable without activated Javascript.

At the current state of #263 on, at least two things don't work: the drop down menus and the sub menus in the sidebar navigaion.

Drop-Down Menus

In absence of javascript, the fallback should be either to use CSS-hovers to still have the drop-down menus working, or alternatively, to provide all the functions at the linked page. Completely missing is e.g. the login / logout facility

Sidebar Navigation

On clicking on the sections headers (like Issues), the new page should have the sub-entries opened by default.

Side remark

An alternative to all that (or at least some of it) could be to drop non-javascript support. Some areas, like issue filters, My-Page customizations can't work without javascript without serious re-architecture. So it might make sense to drop that completely and thus allows us move to a fully-pollished jQuery-UI faster.

What do you think?

Related issues

related to Feature #263: New layout Closed 2011-03-06
related to Feature #658: Include jquery and jquery ui Closed 2011-10-13


Updated by Eric Davis at 2011-10-13 11:53 pm

I'm inclined to drop non-javascript support for our primary audience.

  • It's pretty safe to assume that most Internet browsers use JS now.
  • Some internal networks might turn off JavaScript but in those cases ChiliProject is probably considered an internal app and allowed to use JS.
  • Many mobile browsers support JS now.
  • I think some screen readers also support JS (needs to be confirmed).

On a pragmatic level I would group non-javascript support with our IE6 support: we'd support it if it makes sense, isn't that much trouble, or someone supplies code for it.

We could add a text warning at the top of the page too if it's needed: "This site uses JavaScript which is disabled or not working in your browser. Some parts of the site will not be accessible or functional with it."

Also available in: Atom PDF