[ http://issues.apache.org/jira/browse/TOMAHAWK-581?page=all ]
Martin Marinschek resolved TOMAHAWK-581.
----------------------------------------
Fix Version/s: 1.1.4-SNAPSHOT
Resolution: Fixed
Assignee: Martin Marinschek
With your proposed optimal solution, you'll essentially make the id-handling of
JSF invalid - you cannot have more than one component of the same id in
different forms then.
I've reduced the exception to a warning though.
regards,
Martin
> Focus component cannot focus controls within a subview.
> -------------------------------------------------------
>
> Key: TOMAHAWK-581
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-581
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Affects Versions: 1.1.5-SNAPSHOT
> Reporter: Chad Lyon
> Assigned To: Martin Marinschek
> Priority: Minor
> Fix For: 1.1.4-SNAPSHOT
>
> Attachments: FocusPatch_08-03-2006.diff
>
>
> The focus control only searches it's parent UINamingContainer for the control
> with "id" as specified by the "for" attribute. Therefore controls contained
> in subviews cannot be focused by the focus control. There is a work around
> for this (see below) but an optimal solution would be to have the focus
> control ascend to the HTMLForm component and search all UINamingContainers
> for the control with "id" as specified by the "for" attribute.
> The work around involves removing the Exception thrown by the focus component
> when a search for the control with "id" as specified in the "for" attribute
> fails. By doing this you can place a focus control in the parent UINaming
> container as well as in all subviews and the focus component that finds the
> control will be the one that generates the javascript to focus the control it
> found. A patch for the workaround is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
