[
https://issues.apache.org/jira/browse/TAPESTRY-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490187
]
Joseph Chen commented on TAPESTRY-1113:
---------------------------------------
Is this problem fixed in 4.1.1? I am using the official 4.1.1 distribution
from the tapestry.apache.org website. I have the same problem as the previous
poster, Robert.
We have a Dialog that contains a form. The dialog is initially hidden as well
as set to style="display:none". In IE6, I'm still seeing a error saying "Can't
move focus to the control because it is invisible, not enabled, or of a type
that does not accept the focus." The error only shows up in IE6 (No problems
in Firefox 1.5).
This is a regression from the 4.0.x Tapestry + Tacos 4.0 because the code used
to work fine. It's only when migrating from 4.0.x to 4.1.1 that this problem
shows up.
> 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: Framework, JavaScript, tapestry-core
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
