On 5 March 2011 08:21, Bill van Melle <[email protected]> wrote:
> On Fri, Mar 4, 2011 at 4:44 AM, Greg Brown <[email protected]> wrote: > >> I had a similar thought. Unfortunately, making a Window focusable will >> break apps that currently call window.requestFocus() to focus the content >> component. Those apps would have to change to call >> window.getContent().requestFocus(). That's not out of the question, but >> seems wrong - container focusability was added primarily to support >> composite components like Spinner rather than layout or navigation >> components, or windows. >> > > Would it be reasonable for Window#requestFocus to attempt to set focus to > its child, and if that failed, to take it itself? > Greg proposed a similar thing for the TabPane/Accordion issue https://issues.apache.org/jira/browse/PIVOT-610?focusedCommentId=12902717&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12902717
