275220 - some DOM3 Events interfaces are not frozen but part of the sdk

Status: RESOLVED WONTFIX

(Core :: DOM: Events, defect)

Description

[Christian :Biesinger (don't email me, ping me on IRC)]

see bug 124990 comment 33. that bug (attachment 101794 [details] [diff] [review]) added these interfaces
to the sdk:
nsIDOM3DocumentEvent.idl
nsIDOM3EventTarget.idl
nsIDOMCustomEvent.idl
nsIDOMEventGroup.idl

but none of them are frozen, and in fact the W3C spec (DOM3 Events) has changed.

Comment 1

[Darin Fisher]

Ugh... maybe we need to freeze these as-is since they have been in the SDK for
so many releases?  (since 2002!)

Comment 2

[Benjamin Smedberg]

I think we should definitely not change these interfaces. However, I don't think
we should promise that future geckos will always implement them.

Comment 3

[Darin Fisher]

@status SORT_OF_FROZEN ??? ;-)  I'm not sure I know what that means.  We've
tossed around the idea of deprecating other frozen interfaces when better ones
are created, but it remains to be seen when those "future geckos" will appear.

Comment 4

[Peter Van der Beken [:peterv]]

You're proposing that we freeze DOM interfaces that don't correspond to the
published DOM specifications?

Comment 5

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I think they should be removed from the SDK.

Comment 6

[Darin Fisher]

> You're proposing that we freeze DOM interfaces that don't correspond to the
> published DOM specifications?

I'm saying that this is a very ugly situation.  I'm not happy with freezing bad
interfaces, but they have been apart of our official SDK for two years now! :(

We can try to find out if any embedders or extensions are using these with the
expectation that they are frozen because they included in the SDK, and perhaps
if no one responds to the inquiry, then we proceed to remove them from the SDK.

Comment 7

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

Since everything is unfrozen now, I assume I can mark this as wontfix?