While I think could be a good idea, I respectfully submit that it
should not be a priority /right now /

Then it has to be written down somewhere If it's not, it'll be lost

Dada Mail admins using JS-disabled browsers will still have all kinds of other problems in the
control panel: with the "Subscription Form HTML" screen, with the "Show/Hide
Advanced Options" in the "Send a Webpage" screen, and with pretty much
everything else in admin_js tmpl So the fact that they'll be able to easily
switch to another list's control panel that has all those same problems
won't mean all that much to them ;-)

But how many of these features absolutely require Javascript, or,
with slight tweaking, could work correctly without JS?

• The Subscription Form HTML shows the HTML form code you need,
  without JS intervening, the JS is just sugar to tweak it slightly
  The form to customize this code could be hidden if no Javascript
  support is available The form could be rewritten to be powered by
  Perl, with a slight loss of immediate feedback (It's also some of
  the oldest code in the program )

• The Show/Hide Advanced options is only on that one screen If we
  wanted to, we could have that div visible by default and hide it on
  page load, no problem

• A lot of the JS that's used in the admin is to either help you
  check a lot of checkboxes at once, or used as a back button

Like I said, the JS functions, /as it stands now/ could be much
better engineered to not be a requirement, but an optional feature
that anyone that has JS turned on could use - which hopefully is a
large majority of the users of the program

(C) is all that's needed to make things shippable for 2 10 Everything else, including Justin's above-quoted request, can be moved down the roadmap to 2 11, with a collective understanding that if we do happen to get to something earlier
than that, it'll just be an extra little bonus

Wait - so one feature request gets no priority, another (yours) gets
so much priority that we won't even ship the product if it's
missing? :) I also think there's a few more things needed to make
2 10 shippable, if not just some more, "in the wild" testing

I propose that at the very least we revisit the JS in Dada Mail that
I admit is getting crufty, as most of it was written when I was 19
and making shopping carts out of Javascript for some inane reason

In conclusion:

• I don't think I've ever gotten a report that they thought Dada Mail
  was broken because they didn't know Javascript was required

• I think the Javascript that I've written over the years is crufty,
  and needs a refresh Shane, you put in some links to articles about
  good JS style that I'll go through when I get a minute;

• I think the, "Javascript Required" text that Shane has put in is
  "good enough" for now

Justin Simoni