Ticket submit should trigger form update

[djones@…]

If TracFormsPlugin is used to embed a form within a ticket, the embedded form will have a Submit button, and so will the ticket.

A user might enter data in BOTH the embedded form and in the ticket fields. If the user then selects the ticket's Submit button, changes to the form will be lost. Users must be trained to always submit the embedded form first.

It would be desirable for the ticket Submit button to also trigger the embedded form's Submit button.

(Bonus points for only triggering the embedded form if new or changed data is present, but this strikes me as a much more challenging task.)

[Steffen Hoffmann]

True, this is according to my own observations. And I remember someone else asking about this before.

But it's really hard to achieve due to problems related to HTML form scopes:

• Sending two forms in one request simply doesn't work. I remember vaguely a custom hack on-top of TracForms circumventing that limitation using iframes, but this was in-acceptable for me as too complicated and browser-depended, and I still fell so.
• Nesting forms doesn't work at all by HTML standard.
• Fundamental changes to ticket editor are beyond my current capabilities and time constrains.
• Some way of caching TracForm fields input is the nearest candidate. Probably this will interfere with the other AJAX page update mechanism running for ticket preview since Trac 0.12, but I can't think of another solution now.

Patch/suggestions welcome for taking this nearer to a solution.