I agree Fredrik, but how feasible is that? Say you have two buttons - one called Draft, the other Publish. Pressing them uses JS to set the value of the status field before submitting the document. With no JS what would happen? Nothing. The form is broken! How can this degrade without a complete rethink of how it works. Instead you would need one standard submit button and a toggle status field with options of Draft or Published.
If you going to support the use of no JavaScript, why not just use none in the first place? The only time I can see degrading being useful is with rollover menus and other DHTML. With applications and forms it's best avoided altogether.
I agree Fredrik, but how feasible is that? Say you have two buttons - one called Draft, the other Publish. Pressing them uses JS to set the value of the status field before submitting the document. With no JS what would happen? Nothing. The form is broken! How can this degrade without a complete rethink of how it works. Instead you would need one standard submit button and a toggle status field with options of Draft or Published.
If you going to support the use of no JavaScript, why not just use none in the first place? The only time I can see degrading being useful is with rollover menus and other DHTML. With applications and forms it's best avoided altogether.