Form (and FormInjector) should use the (new) MarkupWriterListener interface to
place the hidden field(s) in an appropriate location
-----------------------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2379
URL: https://issues.apache.org/jira/browse/TAPESTRY-2379
Project: Tapestry
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.0.11
Reporter: Howard M. Lewis Ship
A <form> tag can often go in places where an <input> tag can not. Currenty,
Tapestry's Form component addesses this by creating a <div> to contain the
hidden <input> fields.
As we're doing more dynamic things with Ajax, such as injecting a new <tr>
element into an exiting <table>, this is getting problematic. An <input>
nested inside a <tr> or <table> element is not valid XHTML. We really need to
wait until a good injection point arrives (i.e., we see an <input> or a
<select> or <textarea>, or any of a number of block elements such as <p>,
<span>, <div>, <td> or <th>).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
