Skip to main content

Bug Tracker

Side navigation

#14538 closed bug (wontfix)

Opened November 13, 2013 10:04PM UTC

Closed December 06, 2013 06:00PM UTC

Document Ready doesn't fire ever, after an exception is thrown by a callback

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.7.2
Keywords: Cc:
Blocked by: Blocking:

See the following for an example

We are working on third party javascript and have one site that our tag never fires document ready in. We then discovered that it is because they have an exception in one of their callbacks.

This was not expected behavior. Is this by design? Is there a work around?

The site we are seeing it in is using 1.7.2 but we are seeing this behavior in 2.0+

Attachments (0)
Change History (1)

Changed December 06, 2013 06:00PM UTC by timmywil comment:1

resolution: → wontfix
status: newclosed

Thanks for opening an issue.

This issue has been debated and we decided that it is better than the alternatives.

An uncaught exception is more easily debugged. If it is third party javascript, I suggest opening an issue in their repository.