The Triage interface has turned up a latent bug in the workflow system related to using it multiple times on a single page. This got me thinking that as the number of modular markup systems increase, the chances for a name/ID/CSS class collision is going to increase. To try and control this, I think we need to all agree on some form of naming convention for at least the aforementioned 3 items. Something like "<namespace>_<resource>_<text>" would be my suggestion (so for the text field in set_owner control in the reassign action for ticket #1 this would yield id="defaultworkflow_1_reassign_set_owner"). Some things don't relate to a resource, so they could obviously leave that part out. While this does make things a bit more verbose, I think the long-term benefits to collision avoidance are worth it. I don't know much about the new Context system, but perhaps this could be integrated into that?
--Noah
signature.asc
Description: OpenPGP digital signature
