If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Make nsIInputStream::Read scriptable (or explain in IDL comments why it mustn't be scriptable)

RESOLVED WONTFIX

Status

()

Core
XPCOM
--
enhancement
RESOLVED WONTFIX
7 years ago
7 years ago

People

(Reporter: WeirdAl, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Having to create a scriptable input stream for most input streams is a big pain point.  I'd really love it if we didn't need to do that.

C++ code is smart enough to have method overloading, so if it means having two Read methods, fine.  (I'm not sure XPIDL will allow that, though.)
It's not scriptable becauase it uses nonscriptable types in its signature.  This seems obvious enough that it doesn't need comments.

xpidl doesn't allow "method overloading" at the moment.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 2

7 years ago
(In reply to comment #1)
> It's not scriptable becauase it uses nonscriptable types in its signature. 

You missed my point.  Why does it use non-scriptable types?  Can we rewrite the interface so it doesn't?

Comment 3

7 years ago
Because the current signature is efficient, and none of the scriptable types are especially efficient. We are not going to be rewriting nsIInputStream, the churn doesn't justify the benefit.
You need to log in before you can comment on or make changes to this bug.