tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Ramírez Vique (JIRA) <tapestry-...@jakarta.apache.org>
Subject [jira] Commented: (TAPESTRY-1113) Form component focus parameter not working in 4.1.1
Date Sun, 21 Jan 2007 12:06:30 GMT

    [ https://issues.apache.org/jira/browse/TAPESTRY-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466321
] 

Robert Ramírez Vique commented on TAPESTRY-1113:
------------------------------------------------

I have tried this feature in IE6, but this gives some problems. Seems that IE6 doesn't understand
as hidden the fields inside a hidden dialog.

My situation is really similar to Greg's situation, I have a form, there is a hidden dojo
dialog (this dialog is inside a hidden div,style=display:none, to avoid render it before dojo
is executed). I get a javascript error saying that the focus cannot be set to an invisible
field. Then it causes the rest of javascript code to not be executed (also the dialog).

I supose there should be a better way to solve it (I am not an javascript expert) but maybe
with a javascript try-catch will solve the problem of the javascript exception which prevents
the rest of the code to be executed.

> Form component focus parameter not working in 4.1.1
> ---------------------------------------------------
>
>                 Key: TAPESTRY-1113
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1113
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Core, Framework, JavaScript
>    Affects Versions: 4.1.1
>            Reporter: Greg Woolsey
>         Assigned To: Jesse Kuhnert
>             Fix For: 4.1.1
>
>
> Regression from 4.0.x - there is no code that outputs JavaScript to tell the page which
form to focus, so no form element gets the initial focus.
> Perhaps this could be done as an optional parameter to tapestry.form.registerForm(id).
 If multiple have focus set, last one wins?  Users have to manage that to avoid ambiguity,
as they do now.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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


Mime
View raw message