[
https://issues.apache.org/jira/browse/WICKET-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595827#action_12595827
]
Johan Compagner commented on WICKET-1607:
-----------------------------------------
applied
> addDomReadyEvent unreliable for Safari
> --------------------------------------
>
> Key: WICKET-1607
> URL: https://issues.apache.org/jira/browse/WICKET-1607
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta4, 1.3.0-rc1, 1.3.0-rc2, 1.3.0-final, 1.3.1,
> 1.3.2, 1.3.3
> Environment: Safari 3.1.1
> Reporter: Nathan Hamblen
> Assignee: Johan Compagner
> Fix For: 1.3.4, 1.4-M2
>
> Attachments: safari-domready.patch
>
>
> Because Safari doesn't support an onDomReady event, wicket-event.js emulates
> that behavior using timeouts when that browser is detected. However, the
> timeout is only set once, for 10ms; window.setTimeout() does not produce a
> repeating timeout. If the document object is not ready at that point, the
> registered functions are never called. Often it is ready, so the bug is
> masked.
> I discovered this problem in a page that uses the DateTimeField component,
> which uses onDomReady for its initialization. Sometimes the component works
> fine, other times nothing happens when you click. It's a fairly complicated
> page that apparently Safari may spend more than 10ms building.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
