I'm not sure why the upgrade causes this problem, but the error you are seeing is associated with having a Select component and not assigning a specific component id to it. The default component id is then "select", which is then the default client side id, which is in conflict with the the select() function Prototype adds to DOM elements. Later versions of Tapestry do a better job of "reserving" key ids to prevent such client-side collisions.
Ah, the client-side initialization error is keeping some of the LinkSubmit <span> elements from being converted to <a> elements. This is the likely change; Tapestry was changed to render LinkSubmit components as a <span> and used initialization to rewrite the element into an <a> tag (this helps prevent problems where a user clicks the link before the page has fully initialized). On Mon, Apr 18, 2011 at 11:40 AM, Dmitriy Vsekhvalnov <dvsekhval...@gmail.com> wrote: > Is it broken? After upgrade from 5.1.0.5 found that all LinkSubmit stop > working. > > Debugging shows JS exception: > > 'TypeError: Property 'select' of object #<HTMLFormElement> is not a > function' > > inside tapestry.js createHidden() function. > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
