Closed Bug 9604 Opened 25 years ago Closed 25 years ago

Trigger callbacks don't report download failures

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P2)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dveditz, Assigned: dveditz)

References

Details

(Whiteboard: reviewed fix in hand)

Multiple-trigger callbacks work and report errors that arise in the script, but they don't report failures in the download, failures extracting or launching the script, or failures that blow the script out of the water such that it doesn't call AbortInstall() or FinalizeInstall().
Status: NEW → ASSIGNED
Severity: normal → major
Target Milestone: M9
Priority: P3 → P2
adjusting priority
Blocks: 11171
Depends on: 8138
Target Milestone: M9 → M10
Whiteboard: reviewed fix in hand
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Build 1999-10-20-09-M11(WIN), 1999-10-20-08-M11(MAC), 1999-10-20-08-M11(LINUX) Verified with the following test cases: http://jimbob/jars/f_9604_badurl.html http://jimbob/jars/f_9604_badscript.html http://jimbob/jars/f_9604_no_xpi.html http://jimbob/jars/f_9604_no_installscript.html There exists a discrepancy between platforms for f_9604_badurl.html. Because this is specific to the type of error versus the general ability of reporting download failures, a new bug will be reported. Marking Verified.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.