tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Balázs Palcsó <palcso.bal...@gmail.com>
Subject Re: "Base form control names of component's id, not allocated client-side id" - why?
Date Thu, 27 Aug 2015 23:02:09 GMT
Hi Kalle,

I am not sure what is the reason, but I opened an issue after this change:
https://issues.apache.org/jira/browse/TAP5-2482 , because my tapestry
testify tests started to fail due to this.

Regards,
Balazs

On 27 August 2015 at 22:19, Kalle Korhonen <kalle.o.korhonen@gmail.com>
wrote:

> In 22bd2c14b3c7d91ebd97cbc264882552c12044f7 (since 5.4-beta-31), Howard had
> changed the form control name to be based on component's simple id instead
> of the component's client-side id. This change is not based on any open
> issue, so I'm just trying to find the reason for the change?
>
> Kalle
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message