[
https://issues.apache.org/jira/browse/TAPESTRY-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527104
]
Andreas Andreou commented on TAPESTRY-1692:
-------------------------------------------
Yes - this is needed cause focus can truly break in many different ways and it
may not be tapestry's fault.
A recent example of mine was with dojo:Editor - its focus may end up being
called before it manages to load
its 'internal' iframe
> tapestry.form.focusField quirks!
> --------------------------------
>
> Key: TAPESTRY-1692
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1692
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1.2, 4.1.3
> Reporter: Andrea Chiumenti
> Assignee: Andreas Andreou
> Fix For: 4.1.4
>
> Attachments: form.js.diff
>
>
> When a field is registered for focus but it is inside an hidden element M$IE
> complains about this.
> To avoid this it's enough to put the function inside a try block with an
> empty catch
--
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]
