Closed
Bug 389446
Opened 17 years ago
Closed 17 years ago
FillContentHandlerProperties incorrectly returns NS_ERROR_FAILURE
Categories
(Core Graveyard :: File Handling, defect)
Core Graveyard
File Handling
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9alpha8
People
(Reporter: dmosedale, Assigned: dmosedale)
References
()
Details
Attachments
(1 file)
2.09 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
When a preferred application handler is not specified in the RDF file. This semantic got broken in the refactoring. See the URL attached to this bug around line 845 and onwards for the original codeflow.
Flags: blocking1.9?
Assignee | ||
Comment 1•17 years ago
|
||
Comment on attachment 273640 [details] [diff] [review] patch, v1 Requesting review, as I can't see any way to test this. The case that's being fixed is the protocol handling case, and that code is not accessible from JS. The MIME code eats the error, and I have yet to figure out a way to tell the difference between the error and success cases from JS, though one may exist.
Attachment #273640 -
Flags: superreview?(cbiesinger)
Attachment #273640 -
Flags: review?(cbiesinger)
Assignee | ||
Comment 2•17 years ago
|
||
Another mitigating factor of the lack of test here is that this code should be killed before too long as it all ends up in nsHandlerService.js.
![]() |
||
Comment 3•17 years ago
|
||
Comment on attachment 273640 [details] [diff] [review] patch, v1 r+sr=bzbarsky
Attachment #273640 -
Flags: superreview?(cbiesinger)
Attachment #273640 -
Flags: superreview+
Attachment #273640 -
Flags: review?(cbiesinger)
Attachment #273640 -
Flags: review+
Assignee | ||
Comment 4•17 years ago
|
||
Fixed: Checking in nsExternalHelperAppService.cpp; /cvsroot/mozilla/uriloader/exthandler/nsExternalHelperAppService.cpp,v <-- nsExternalHelperAppService.cpp new revision: 1.325; previous revision: 1.324 done
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•