Audit our JS use and make recommendations to ensure degradation where applicable

Not the same, no. Because we're using Drupal 7's #ajax system, our JS usage should be degradable. The problem at this point is the UX aspect, not the technical aspect. We lack the appropriate buttons and labels to have great degradation, and I'd welcome a review / suggestions for the various places we're using AJAX.

Actually, using #ajax does not necessarily give degradability at all. It can take some extra work to get graceful degradation. In the AJAX Example from Examples, if you look at the dependent dropdown example, you see something that works only with JS on. You can't ever access the second-level values with js off. The dependent dropdown with degradation example shows how this has to be done. There's an imitation-of-js-off version so you don't actually have to turn js off. You'll see that a significant interface change is required to take something like a select-driver and make it non-js compatible.

So I guess we should make this a policy question. It's my bet that there are at least a couple places that would require some serious multistep fixup.

Yeah, there are definitely places that need multistep functionality, like on a multi-product Add to Cart form. I just didn't want to change this to a task myself, but if someone wants to take it on now, that'd be great. : )

These are the main points that need auditing / recommendations:

• Add to cart form (multi-value product reference fields)
• Address field - used on checkout, customer profile, and order forms
• Line item manager widget on the order form
• Payment selection checkout pane

There may be other places. If push comes to shove, I'm more interested in front end degradation than I am back end.

Subscribe

The current Behat tests shows that a lot of the tests run without javascript enabled. @jdln and @EndEd if you find any place, where Commerce does not degrade gracefully without javascript, you can create new issues.