Failure to create JS-implemented webidl component always throws NS_ERROR_FAILURE

RESOLVED FIXED in mozilla35

Status

()

defect
RESOLVED FIXED
5 years ago
3 months ago

People

(Reporter: neil, Assigned: neil)

Tracking

({regression})

Trunk
mozilla35
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

I was trying to debug an error whereby accessing navigator.mozApps throws NS_ERROR_FAILURE in Thunderbird.

Fortunately I found a changeset in between where navigator.mozApps broke and where it got converted to webidl where the global navigator property code propagated the actual error, which gave me a chance to debug it.

It would have been nice if you had actually propagated the error instead of just unhelpfully throwing NS_ERROR_FAILURE.
Attachment #8496795 - Flags: feedback?(peterv)
Comment on attachment 8496795 [details] [diff] [review]
Possible patch

Makes sense to me.  r=me
Attachment #8496795 - Flags: feedback?(peterv) → feedback+
McMerge missed this because I wasn't assigned.

https://hg.mozilla.org/mozilla-central/rev/7787a8038654
Assignee: nobody → neil
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Component: DOM → DOM: Core & HTML
Type: enhancement → defect
You need to log in before you can comment on or make changes to this bug.