Chart selection UI

Gervase Markham gerv at mozilla.org
Sun Nov 17 17:04:29 UTC 2002


I'm currently working on generic charting. The design is here:
<http://www.mozilla.org.uk/temp/graph/>

If you look at
<http://www.mozilla.org.uk/temp/graph/select-mockup.html>, you'll see 
that charts have a three-level categorisation. The idea is to use JS to 
update the second and third level lists as selections are made in the 
first and second level lists, respectively.

The big question is: what do we do for people who have JS switched off?

This problem is not comparable to the query page with Products and 
Components, because selecting just a Component to search on is a 
perfectly valid search restriction, whereas in with reports you need to 
select a Category, Sub-category and Name which make a valid data set. 
So, having all the possibilities in each list is not a valid solution.

There are three solutions, none very appealing:

1) Have one big <select> for those without JS, and choose the UI with
    <script> and <noscript>.
   - Everyone downloads the data that makes up the list twice, once in JS
     and once in the big <select>
   - The large select would get really unwieldy.
   - You would have to write the entire JS UI using document.write().

2) Make people without JS submit the form every time they make a
    selection in any of the select boxes.
   - With the speed of b.m.o. at the moment, this would make it take ages
     for people without JS to assemble a report.

3) Require JS to assemble reports (viewing them would work fine
    without.)
   - Now we have things like popup control, I think more people
     are happy to have JS on.
   - This goes against our current policy of not requiring JS.

Thoughts? I'm leaning towards 2), on the basis that it doesn't penalise 
people with JS with an extra download as 1) does.

Gerv




More information about the developers mailing list