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

Status

()

Core
Embedding: APIs
RESOLVED WONTFIX
13 years ago
7 years ago

People

(Reporter: jhp (no longer active), Assigned: Adam Lock)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
nsIDOMWindow2.idl, in dom/public/idl/base/Makefile.in, is listed as
SDK_XPIDLSRCS, which is used for frozen interfaces.  However, this interface is
not actually frozen (no "@status FROZEN").
(Reporter)

Updated

13 years ago
Blocks: 268520
See bug 129602 comment 10.

Comment 2

13 years ago
i'd like access to this property from js. i know there are security concerns,
these can be handled by security checks.

Comment 3

13 years ago
timeless: i don't think that is a pre-req to freezing this interface.  the
change could be made after this interface is frozen.  (if you want that change
to be made, then perhaps you should file a new bug.)

Comment 4

13 years ago
i'm not sure i could make it after you freze the interface...

Comment 5

13 years ago
timeless: The interface is already effectively frozen because it was included in
the Gecko SDK.  What do you mean by your comment?  Why do you think removing
[noscript] cannot be done without changing the ABI for C++ users?
Including this interface in the SDK was clearly an error in light of the comment
I mention in comment 1 of this bug.

If we _do_ have to freeze it, we probably need an nsIDOMWindow3 to handle the
issues mentioned therein.

Comment 7

13 years ago
> Including this interface in the SDK was clearly an error in light of the comment
> I mention in comment 1 of this bug.

Sure, but what's done is done.  Jst agreed that this interface should be frozen.
 nsIDOMWindow3 is where the rest of those nsIDOMWindowInternal things could live.

Comment 8

13 years ago
it would change the interface for anyone implementing nsIDOMWindow2...

Comment 9

13 years ago
timeless: fair enough; i agree that that could be a problem.  i doubt there are
existing implementors outside our source code, but i could be wrong i guess.

Comment 10

13 years ago
i'd agree with you, but when i make that argument later, someone will give me
the argument i gave today. i'm always in a lose lose situation.
QA Contact: apis
We no longer freeze interfaces.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.