Thanks Geoff. It looks like. I have commented the issue.
On 17 April 2014 03:49, Geoff Callender wrote:
> This might be the client-side counterpart of
> https://issues.apache.org/jira/browse/TAP5-2075 ?
>
> On 17/04/2014, at 7:08 AM, Balázs Palcsó wrote:
>
> > Hi,
> >
> > I was trying to apply
I have an interesting question: what happens exactly when user presses
Enter inside a TextField?
Currently I see that form submit works as if it was triggered by the first
available Submit element (in order those elements appear in the form). I
don't think this is correct, but I don't have any ide
Hi Ilya,
As far as I know, this is standard browser/form behavior, regardless of the
web framework you are using (Tapestry, PHP, etc). You can use JavaScript
to change the behavior or CSS to do tricky things, like move the positions
of the submit buttons when they render so that the one you want
That's standard HTML browser behavior; when you hit enter in a text field,
is searches forward for a submit and clicks it. You can perhaps address
this by putting an event handler on the text field itself. I'd have to do
experimentation/research to find the correct event.
On Thu, Apr 17, 2014 a
Try:
http://mail-archives.apache.org/mod_mbox/tapestry-users/201304.mbox/%3cae6d59e6-df9c-4a9c-a0bf-233ab00bc...@hope.nyc.ny.us%3E
There was a thread April 2013 with the
title: AssetsModule.ResourceMinimizer Exception yui compressor
Regards,
Jonathan
On Mon, Apr 14, 2014 at 5:58 AM, John wro
Thanks Howard! That's probably keyDown/keyPressed events and it might be a
little bit complicated when the same textfield acts as a base control for
AutoComplete (of any kind). I'll do some research, too.
On Fri, Apr 18, 2014 at 1:45 AM, Howard Lewis Ship wrote:
> That's standard HTML browser b
