You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Maximilian Weißböck <Ma...@sphinx.at> on 2008/07/09 18:23:18 UTC

T5: Different behavior of Palette Component in FireFox, Safari and IE

Palette Component behaves different in FireFox then it does in Safari and IE

 

If  palette item is moved in FireFox the following events are triggered

  

  onSuccess()

  onSubmit()

 

If  palette item is moved in Safari or IE none of the above events is triggered.

 

Is this suggested to be a bug? Then I would file a Jira Issue.

Tested with FF 3.0, Safari 3.1 and IE 6 (all on Windows)

 

Regards, Max

 


Re: T5: Different behavior of Palette Component in FireFox, Safari and IE

Posted by Martin Grotzke <ma...@javakaffee.de>.
Hi Yunhua,

really good news! We're using 5.0.11...

Thanx for the hint,
cheers,
Martin


On Thu, 2008-07-10 at 07:37 -0400, Yunhua Sang wrote:
> What version of T5 are you guys using?
> 
> I think there was a jira about it and it has been fixed already. see.
> 
> https://issues.apache.org/jira/browse/TAPESTRY-2507 - Palette
> component forces an unwanted form submit under FireFox 3
> 
> Yunhua
> 
> On Thu, Jul 10, 2008 at 5:44 AM, Martin Grotzke
> <ma...@javakaffee.de> wrote:
> > Hi,
> >
> > we experience exactly the same issue: with FF3 the palette submits the
> > form, with FF2 this is not the case. Max, when you submit the issue in
> > jira please send a ping here, so that I can vote :)
> >
> > Cheers,
> > Martin
> >
> >
> > On Wed, 2008-07-09 at 18:23 +0200, Maximilian Weißböck wrote:
> >> Palette Component behaves different in FireFox then it does in Safari and IE
> >>
> >>
> >>
> >> If  palette item is moved in FireFox the following events are triggered
> >>
> >>
> >>
> >>   onSuccess()
> >>
> >>   onSubmit()
> >>
> >>
> >>
> >> If  palette item is moved in Safari or IE none of the above events is triggered.
> >>
> >>
> >>
> >> Is this suggested to be a bug? Then I would file a Jira Issue.
> >>
> >> Tested with FF 3.0, Safari 3.1 and IE 6 (all on Windows)
> >>
> >>
> >>
> >> Regards, Max
> >>
> >>
> >>
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
> 

Re: T5: Different behavior of Palette Component in FireFox, Safari and IE

Posted by Yunhua Sang <yu...@gmail.com>.
Sorry the link was wrong, it should be

https://issues.apache.org/jira/browse/TAPESTRY-2490

On Thu, Jul 10, 2008 at 7:37 AM, Yunhua Sang <yu...@gmail.com> wrote:
> What version of T5 are you guys using?
>
> I think there was a jira about it and it has been fixed already. see.
>
> https://issues.apache.org/jira/browse/TAPESTRY-2507 - Palette
> component forces an unwanted form submit under FireFox 3
>
> Yunhua
>
> On Thu, Jul 10, 2008 at 5:44 AM, Martin Grotzke
> <ma...@javakaffee.de> wrote:
>> Hi,
>>
>> we experience exactly the same issue: with FF3 the palette submits the
>> form, with FF2 this is not the case. Max, when you submit the issue in
>> jira please send a ping here, so that I can vote :)
>>
>> Cheers,
>> Martin
>>
>>
>> On Wed, 2008-07-09 at 18:23 +0200, Maximilian Weißböck wrote:
>>> Palette Component behaves different in FireFox then it does in Safari and IE
>>>
>>>
>>>
>>> If  palette item is moved in FireFox the following events are triggered
>>>
>>>
>>>
>>>   onSuccess()
>>>
>>>   onSubmit()
>>>
>>>
>>>
>>> If  palette item is moved in Safari or IE none of the above events is triggered.
>>>
>>>
>>>
>>> Is this suggested to be a bug? Then I would file a Jira Issue.
>>>
>>> Tested with FF 3.0, Safari 3.1 and IE 6 (all on Windows)
>>>
>>>
>>>
>>> Regards, Max
>>>
>>>
>>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: T5: Different behavior of Palette Component in FireFox, Safari and IE

Posted by Yunhua Sang <yu...@gmail.com>.
What version of T5 are you guys using?

I think there was a jira about it and it has been fixed already. see.

https://issues.apache.org/jira/browse/TAPESTRY-2507 - Palette
component forces an unwanted form submit under FireFox 3

Yunhua

On Thu, Jul 10, 2008 at 5:44 AM, Martin Grotzke
<ma...@javakaffee.de> wrote:
> Hi,
>
> we experience exactly the same issue: with FF3 the palette submits the
> form, with FF2 this is not the case. Max, when you submit the issue in
> jira please send a ping here, so that I can vote :)
>
> Cheers,
> Martin
>
>
> On Wed, 2008-07-09 at 18:23 +0200, Maximilian Weißböck wrote:
>> Palette Component behaves different in FireFox then it does in Safari and IE
>>
>>
>>
>> If  palette item is moved in FireFox the following events are triggered
>>
>>
>>
>>   onSuccess()
>>
>>   onSubmit()
>>
>>
>>
>> If  palette item is moved in Safari or IE none of the above events is triggered.
>>
>>
>>
>> Is this suggested to be a bug? Then I would file a Jira Issue.
>>
>> Tested with FF 3.0, Safari 3.1 and IE 6 (all on Windows)
>>
>>
>>
>> Regards, Max
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: T5: Different behavior of Palette Component in FireFox, Safari and IE

Posted by Martin Grotzke <ma...@javakaffee.de>.
Hi,

we experience exactly the same issue: with FF3 the palette submits the
form, with FF2 this is not the case. Max, when you submit the issue in
jira please send a ping here, so that I can vote :)

Cheers,
Martin


On Wed, 2008-07-09 at 18:23 +0200, Maximilian Weißböck wrote:
> Palette Component behaves different in FireFox then it does in Safari and IE
> 
>  
> 
> If  palette item is moved in FireFox the following events are triggered
> 
>   
> 
>   onSuccess()
> 
>   onSubmit()
> 
>  
> 
> If  palette item is moved in Safari or IE none of the above events is triggered.
> 
>  
> 
> Is this suggested to be a bug? Then I would file a Jira Issue.
> 
> Tested with FF 3.0, Safari 3.1 and IE 6 (all on Windows)
> 
>  
> 
> Regards, Max
> 
>  
>