JS exceptions in nsXBLProtoImpl::InitTargetObjects are not always handled properly

NEW
Unassigned

Status

()

Core
XBL
4 years ago
4 years ago

People

(Reporter: mccr8, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
In some circumstances, like in content/events/test/test_focus_disabled.html, if InitTargetObjects ends up in a JS api call that sets an exception, it doesn't end up getting caught anywhere, so at some random later point you end up hitting an assertion about there being a lingering exception on the context.  I'll try to come up with a C++ patch that demonstrates the issue.
You need to log in before you can comment on or make changes to this bug.