A nice idea, I figure everyone builds up their own mini-library of T5 add-ons!
As for the above, I've just added an 'event' and 'disabled' parameters
and re-named it to 'EventButton'.
Steve.
On 7 September 2011 11:02, Taha Hafeez wrote:
> Hi Steve
>
> Thanks for pointing it out. Well I will rem
Hi Steve
Thanks for pointing it out. Well I will remove the zone and add it to
tawus-addons library. We should have something like
tapestry-extensions containing all these extensions that are not
important enough to be in core but good enough to be the the project
On Wed, Sep 7, 2011 at 8:13 AM,
form.submit vs form.submit() - I can't believe I was diddled by that
old chestnut! I've pointed it out to many others in the past!
I knew it must have been something glaringly obvious and a mistake on
mybehalf - it was too blatant to just flat out not work!
> I've created https://issues.apache.or
I've created https://issues.apache.org/jira/browse/TAP5-1632 for this
defect.
Thanks..
On Wed, Sep 7, 2011 at 3:36 AM, Josh Canfield wrote:
> > If we want to use "cancel" mode submit, then we should give an id to the
> submit component.
>
> This is a defect for sure. Submit should never create a
> If we want to use "cancel" mode submit, then we should give an id to the
> submit component.
This is a defect for sure. Submit should never create an id of submit.
There was something filed at one point, but I haven't taken the time
to track it down. If you want to file a new defect we can prob
Many thanks to Steve Eynon and Taha Hafeez for your valuable time helping me
find a workaround.
And many thanks to Josh Canfield who can point directly about mistake in my
code. Yep, it's because my submit don't have id.
So the conclusion is: If we want to use "cancel" mode submit, then we should
I believe the problem is that the id of your submit button is "submit" which
overrides the form. submit() of the form. Try adding t:id="something" to
your submit button.
I thought this was fixed, but just team into it myself last week.
On Sep 5, 2011 9:13 PM, "Yohan Yudanara" wrote:
> Hi..
>
> I
Hi Yohan,
I prefer to use my own cancel button(using get instead of post)
inspired(read copied/cheated/learnt) from the chenillekit's button.
@Import(library = "cancel-form.js")
public class Cancel implements ClientElement
{
/**
* JavaScript id to be used. If id is not supplied, it will be
Yay! I'm happy I'm not the only one who's noticed this!
[T5.3-beta-1] Submit buttons with t:mode="cancel" do not submit the form
http://tapestry.markmail.org/message/5yrkjtm2nfevear5
I to, would like someone in the know to confirm whether this is
desired behaviour (I'm thinking it's not, but then
oo sorry, I forgot to mention.
I'm using Tapestry 5.2.6
On Tue, Sep 6, 2011 at 11:13 AM, Yohan Yudanara wrote:
> Hi..
>
> I want to use submit button which can bypass client validation.
> Having read this documentation:
> http://tapestry.apache.org/current/tapestry-core/ref/org/apache/tapestry5/c
10 matches
Mail list logo
