Remove nsIDOMArchiveRequest in favor of nsIDOMDOMRequest

RESOLVED WONTFIX

Status

()

Core
DOM
RESOLVED WONTFIX
6 years ago
6 years ago

People

(Reporter: mounir, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
nsIDOMArchiveRequest adds the possibility to access the reader that created the request. I feel like this is rarely going to be used in real life and this is adding more complexity to our code. An example, even our dev engagement team shows examples using the referenced ArchiveReader instead of using the attribute from the request:
https://hacks.mozilla.org/2012/10/archiveapi-read-out-archive-file-contents-introducing-bleeding-edge/

Another point in favour of removing: adding that would be easy. Removing because it is barely used is not.
Jonas, I need your feedback about this.
I'd prefer to keep this as-is. While I agree that for simple examples simply keeping a reference to the reader is easy. But once your code gets more complex it seems nice that you can get to the reader through the information handed to the eventhandler.
can I resolve it as 'WONTFIX' ?
(Reporter)

Comment 4

6 years ago
If both of you disagree, yes...
Yes, I agree with the Sicking's point of view.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.