273436 - nsIDOMKeyEvent not frozen

Status: RESOLVED INVALID

(Core :: DOM: Events, defect)

Description

[Crispin Flowerday (not receiving bug mail)]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041204 Galeon/1.3.18.99
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041204 Galeon/1.3.18.99

While nsIDOMMouseEvent and nsIDOMUIEvent were frozen in bug 161166,
nsIDOMKeyEvent wasn't. I realize this might be intentional (due to all the
DOM_VK key codes), but couldn't find any references in bugzilla or the web about
this interface.

Reproducible: Always
Steps to Reproduce:

Comment 1

[Boris Zbarsky [:bzbarsky]]

nsIDOMKeyEvent is not a W3C DOM interface.  The W3C DOM Level 2 Events
specification does not define anything useful about key events.

This is why it was not frozen in bug 161166.

I would prefer it not be frozen until the DOM _does_ define key events
(presumably in the context of the WebApps WG), as we may or may not need to
modify the interface to comply with the resulting specification.

There is the W3C DOM Level 3 Events note that does define a KeyboardEvent
interface, but we don't implement that yet, and it's not a Recommendation, so we
may well never do so.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Crispin Flowerday (not receiving bug mail)]

Well, this still isn't interface still isn't frozen, so this bug is still valid.

Comment 4

[Anne (:annevk)]

Setting to NEW which hopefully stops gervspam. :-) DOM Level 3 Events is the
specification that browsers should implement. The only reason it was published
as a W3C Note was because there was not enough time to finish it.

Comment 5

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Now, all interfaces are not frozen. I think that we don't need to keep this open.