One use case I have for putting javascript in .tml is to get a function
to execute after a zone update. Due to Tapestry attaching onclick event
handlers to actionlinks (as opposed to using onclick attribute), it's
not that easy afaik to guarantee your own method will get called
afterwards (the DOM
Yes, it's true it might not be the fastest or easiest way, but
I think it's good that Tapestry "forces" you to things the right way.
Nicolás.-
Hi Cameron,
On Thu, Dec 16, 2010 at 8:03 AM, Newham, Cameron wrote:
> > Should I be adding my JavaScript with JavaScriptSupport (and if so,
> > where is documentation or an example? The only mention of JavaScript I
> > can find is in the HOW-TOs which show it being added to the .tml file
> > dire
Thanks Andreas.
Yes, name attribute was the problem. I've changed to using getElementById and
it's working again.
c.
-Original Message-
From: andre...@gmail.com [mailto:andre...@gmail.com] On Behalf Of Andreas
Andreou
Sent: 16 December 2010 10:12
To: Tapestry users
Subje
I dont like this way of refering to nodes ( document.entryForm.oosComment )
i'm not sure how many browsers fully support this but it looks like
this can work
when nodes have the name attribute set.
If i remember correctly, T5.1 used to include a name in each form but
this was removed
in 5.2 - see
