Em Wed, 09 Dec 2009 16:10:44 -0200, Vangel V. Ajanovski
escreveu:
- t:id="my submit" - works
AFAIK, t:id can't have a space on it.
- id="my submit" does not work
Does this mean that theoretically a single component can have two id-s?
One tapestry id, and another non-tapestry one?
Yes
On 09.12.2009 11:24, sandeepraj singh wrote:
> Its because, when you do not assign t:id to a submit button, it assigns
> name="submit"
> which has a conflict with any other submit in your page(even through java
> Script)
>
> i got it working with t:id="My Submit" then even on Change works.
>
Hu
https://issues.apache.org/jira/browse/TAP5-947
On Wed, Dec 9, 2009 at 1:17 PM, sandeepraj singh <
sandeepraj.si...@atosorigin.com> wrote:
>
> Hi Inge,
> I am not able to raise the jira since i am sitting behind a firewall.
> Do you mind raising it?
>
> Thanks
> Sandeep
>
>
> Inge Solvoll-2 wrote:
Hi Inge,
I am not able to raise the jira since i am sitting behind a firewall.
Do you mind raising it?
Thanks
Sandeep
Inge Solvoll-2 wrote:
>
> I think this should be a JIRA issue in T5. If you don't specify an id for
> a
> submit, T5 generates name="submit", which breaks form javascript. T5
>
I think this should be a JIRA issue in T5. If you don't specify an id for a
submit, T5 generates name="submit", which breaks form javascript. T5 should
generate a safe default name for submit component.
On Wed, Dec 9, 2009 at 11:24 AM, sandeepraj singh <
sandeepraj.si...@atosorigin.com> wrote:
>
Hi,
Its because, when you do not assign t:id to a submit button, it assigns
name="submit"
which has a conflict with any other submit in your page(even through java
Script)
i got it working with t:id="My Submit" then even on Change works.
This is such an irritating error that we have put it our
What was your way out mite.How did you get it working
But anyways, do you think writing a java script for submitting a select
should be the ideal way that it should be working?
Thanks
Sandeep
Mite wrote:
>
> At last. This way works.
>
> This is the second time you get me out of the mud. :)
I solved this problem just a few weeks ago myself :) It is a very bad bug
that is very hard to track down, the only error is "submit is not a
function".
The solution is to assign an id to your submit button, like this: . You should always do that anyway, it makes code clearer
and it is easier to t
Em Tue, 08 Dec 2009 22:33:40 -0200, Vangel V. Ajanovski
escreveu:
But, the bad thing is that here Thiago's solution does not help - with
it I get an Event.observe is not a function
And now it does not work even in IE.
This is a Prototype function, documented here:
http://www.prototypejs.o
I removed the submit button and it works indeed.
Thank you for the answer.
--
View this message in context:
http://old.nabble.com/Select-does-not-submit-form-on-change-tp26687467p26703632.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
On 09.12.2009 01:33, Vangel V. Ajanovski wrote:
>
> But, the bad thing is that here Thiago's solution does not help - with
> it I get an
> Event.observe is not a function
> And now it does not work even in IE.
>
>
Now I am replying to myself ;)
Of course it doesn't work - prototype is not au
Sorry, but there might be some problem with the mailing list, my message
was considered as a SPAM and first the text was removed from the
message, and the next time I got info that it was considered as SPAM.
I am sending the message again.
On 08.12.2009 02:47, Mite wrote:
> I have written this co
smime.p7s
Description: S/MIME Cryptographic Signature
At last. This way works.
This is the second time you get me out of the mud. :)
Thank you
--
View this message in context:
http://old.nabble.com/Select-does-not-submit-form-on-change-tp26687467p26697258.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
I will be more specific then.
What you need to do is:
- Use Firefox and Firebug (or some other request monitoring tool) to see
what happens when you select something in your select. Is any event trigered
in the browser. Is something sent to the server?
- Check on the server side if the page clas
Em Tue, 08 Dec 2009 09:18:59 -0200, Mite escreveu:
No, I just have the function:
void onSubmit() {
System.out.println("Value changed!");
}
Try using onSuccess() instead of onSubmit().
By the way, instead of relying on onchange="", use Prototype events:
Event.observe(
No, I just have the function:
void onSubmit() {
System.out.println("Value changed!");
}
which prints to console when a submit is made, but it does not print
anything when I change the value.
Are you using some debug tool to verify if a request is sent to the server?
Like firebug i
You're not giving us very much information to work with here...
Are you using some debug tool to verify if a request is sent to the server?
Like firebug in firefox? Are you getting a javascript error when you select
something?
On Tue, Dec 8, 2009 at 11:58 AM, Mite wrote:
>
> Thank you for the r
The only way I got this to work was via Javascript called from the
select to do the submit.
-Original Message-
From: Mite [mailto:mitemeis...@gmail.com]
Sent: 08 December 2009 10:58
To: users@tapestry.apache.org
Subject: Re: Select does not submit form on change
Thank you for the
Thank you for the reply.
It does not make any difference. Still the same result.
This is really bad. Trying to get to work an event on a select for a whole
day.
It is so much easier with .NET or only JavaScript and HTML.
Try
this.form.submit()
--
View this message in context:
http://old.n
Try
this.form.submit()
On Tue, Dec 8, 2009 at 2:47 AM, Mite wrote:
>
> Hi
>
> I am trying to attach an event to a select. The guys that worked before me
> used this model.
> http://wiki.apache.org/tapestry/Tapestry5SelectObject
>
> I have written this code so far:
>
>
> labelField="literal:co
21 matches
Mail list logo
