Yes,
So good. I've setted the showLoading text to subimmit button, but I've
forgot to remove in the div.
We must take it out from both.
Thanks a lot man, You've saved my job. :-)
Regards,
Felipe Rodrigues
Musachy Barroso wrote:
>
> it is the "bug" I've been talking about all time long :), th
it is the "bug" I've been talking about all time long :), there are other
threads about this on the list. The thing is: before the request is made,
"loading..." (or the loading text) is set as the content of the targets, in
FF, this doesn't destroy the form(form to be submitted), but in IE it does
I also don't thing it is a generic bug. Not so sure as well if it is a real
bug. But to make sure we I would like somebody else try to reproduce this
issue.
The scenario is, a form with some fields that are not Action Attributes, try
to get these fields using ActionContext or even the ParametersAw
I'm not sure about that, there is a ton of examples using targets in
showcase, I'm not saying there isn't a bug, just that if there is one is not
as generic as "not working with targets at all". Keep going, I got the
feeling you will find it soon :)
musachy
On 4/23/07, Felipe Rodrigues <[EMAIL P
Ok. I found out one more thing.
I think we are getting close to the real bug.
Button (or even anchor) doesn't works when I use targets. If I remove
target, then all the thing works fine.
But I need to refresh my screen after submit this form. I tried use
notifyTopics, but how can I say to some div
Anchor and Submit use the same Widget. That's weird.
musachy
On 4/23/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
I've tried it.
An interesting thing is: With anchor it works fine. using . I can do
my
system using anchor, but I would suggest someone else try do that in order
to figure out
I've tried it.
An interesting thing is: With anchor it works fine. using . I can do my
system using anchor, but I would suggest someone else try do that in order
to figure out if it is a real bug or not. If so, could create a JIRA Issue.
What do you think? Did you tried to reproduce the same issu
Try setting formId="formVariaveis" in the submit button.
musachy
On 4/23/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
Hi,
After a weekend, we are back to reality...
Some other clue to help me fix this issue?
Thanks,
Felipe
Felipe Rodrigues wrote:
>
> yes. But this is not the div I'm
Hi,
After a weekend, we are back to reality...
Some other clue to help me fix this issue?
Thanks,
Felipe
Felipe Rodrigues wrote:
>
> yes. But this is not the div I'm trying to update.
>
>
> Musachy Barroso wrote:
>>
>> Is the submit button inside the div? something like:
>>
>>
>>
yes. But this is not the div I'm trying to update.
Musachy Barroso wrote:
>
> Is the submit button inside the div? something like:
>
>
>
>
>
>
> musachy
> On 4/20/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
>>
>>
>> DEBUG: widget ID collision on ID: btGravar. I've changed this ID
I puzzled my last email. Sending again in the right order.
The message was: "DEBUG: widget ID collision on ID: btGravar."
But I already changed the Id. The problem keeps up.
Thanks
Felipe Rodrigues wrote:
>
> DEBUG: widget ID collision on ID: btGravar. I've changed this ID and I
> don't get
Is the submit button inside the div? something like:
musachy
On 4/20/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
DEBUG: widget ID collision on ID: btGravar. I've changed this ID and I
don't
get this error anymore.
But the problem persist. IE doesn't send any parameter.
That was t
DEBUG: widget ID collision on ID: btGravar. I've changed this ID and I don't
get this error anymore.
But the problem persist. IE doesn't send any parameter.
That was the message!
Musachy Barroso wrote:
>
> Well we are getting closer then, it is not related to the ActionContext
> (which I doub
Well we are getting closer then, it is not related to the ActionContext
(which I doubted anyway) but to ajax. Set debug="true" on the head tag and
see if there are any errors. The other thing, is the submit button, or the
anchor inside the div that you are trying to update (if it is then you need
Hi again,
I tried without the theme="ajax" in the submit button. It worked even at IE,
but then, I lost the ajax behavior. I need update a div. So I think it is a
bug of ajax theme vs IE.
What do you think?
Thanks,
Felipe
Felipe Rodrigues wrote:
>
> Thanks for the help,
> Now I'm trying wit
Thanks for the help,
Now I'm trying with this simple form, simpler than the first. For my
surprise I got the same problem.
In Firefox works, in IE doesn't.
Here goes my code, first the part I getting the ActionContext and getting
the parameters:
ActionContext ac = ActionContext.getContext();
Map
You could compare what is getting submitted to the server by both FF and IE.
But it does sound weird. Try to narrow it down to a simple form, with a
simple action, with no extra-interceptors, etc.
musachy
On 4/20/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
I don't want to screw up, but d
I don't want to screw up, but doesn't it sound like a bug?
I have nowhere more to look for a solution.
{}
Felipe
Felipe Rodrigues wrote:
>
> Sure,
>
> Pls, excuse the names in portuguese. It is not a simple form, and it is in
> this way because it is dinamicaly generated.
>
> --
Sure,
Pls, excuse the names in portuguese. It is not a simple form, and it is in
this way because it is dinamicaly generated.
- BEGIN OF CODE
---
Variável
Unid
Valor
Valor
Can you post the form that you are submitting?
musachy
On 4/20/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
Hi guys,
I'm using ActionContext to get get some fields from a form that is
dinamically generated.
So, I use, ActionContext.getContext( ).getParameters( ) that returns me a
Map.
It
20 matches
Mail list logo
