You're not the first one :) I believe this has been fixed for 5.2. https://issues.apache.org/jira/browse/TAP5-947
On Tue, Jun 8, 2010 at 9:42 AM, Paul Stanton <p...@mapshed.com.au> wrote: > I'm keen for peoples opinions regarding whether this is a bug or not. > > <input t:type="Submit" value="submit" /> > >>> > <input value="submit" name="submit" type="submit></input> > > this causes problems because since the fields name is 'submit' the > javascript function 'form.submit()' is discarded. This just cost me about 2 > hours figuring out why linksubmit components no longer worked on my page. > personally, i think this is a bug. > > obviously, you can avoid this by giving your submit component a t:id: > > <input t:type="Submit" t:id="mySubmit" value="submit" /> > >>> > <input value="submit" name="mySubmit" type="submit></input> > > which exposes my second issue with this component - i would expect the > input's 'id' attribute to also equal 'mySubmit' as this is what other > tapestry form components do. in order to get my desired markup, i need to do > the following: > > <input t:type="Submit" t:id="mySubmit" id="mySubmit" value="submit" /> > >>> > <input id="mySubmit" value="submit" name="mySubmit" type="submit></input> > > p. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
