Did a small bit of research and testing and it seems either "disabled" or "disabled=disabled" will work on the various form elements. It also seems disabled='true' works, which I like the best... To allow disabled=disabled or disabled=true in the markup we could simply add "disabled" to the BOLTattrs for the various form elements.
Of course, typing 'disabled' is shorter and only requires one small bit of code in the forms markup, so my first thought was to go that route. But there is a disadvantage however: it could get confused with a label, name, or value. Suppose I wanted a button called "disabled" or even a text field preset to "disabled": [submit label="disabled"] [text name=field value='disabled'] Using your suggested code, BoltWire would be confused into thinking these items should be disabled when really you just want that word in your label or preset value. And it works the other way. Suppose I wanted a blank text field that was disabled. Do [text field disabled] And it will not only disable the box, but take disabled as the preset value. Which we don't want. So it seems to me, the best option is to add it by default to the BOLTattrs for the various form elements and have people enter disabled=true rather than just disabled to avoid confusion. Cheers, Dan -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
