Closed Bug 493971 Opened 15 years ago Closed 13 years ago

Implement KeyboardEvent.location (dom3)

Categories

(Core :: DOM: Core & HTML, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 166240
mozilla1.9.2

People

(Reporter: asaf, Assigned: asaf)

References

()

Details

KeyboardEvent.keyLocation from the dom3-events spec is needed for bug 98160.

Since I'm not going to implement the rest of this spec, I wonder if it's better to name it mozKeyLocation for the time being. What was our policy in the past? Should I create a new interface for it or should i use the NS interface?

CCing intuitively, feel free to unCC yourself :)
Note, DOM 3 Events is still (unfortunately) just a draft.
I know, but it's in this state since I started contributing to Mozilla a the very least :-/

What's our "policy" in this case. Is it OK to implement it as mozKeyLocation for now?
I'd say it would be very useful for DOM 3 Events to start implementing things.
But yes, perhaps with moz-prefix for now.
As the slacker current editor of DOM3 Events, I don't expect keyLocation to change.  I would consider it to be stable, and will try to move DOM3 Events forward soon.
Looks like it changed to be just "location" in the latest draft.
Summary: Implement KeyboardEvent.keyLocation (dom3) → Implement KeyboardEvent.location (dom3)
Any chance we will get this feature implemented for 1.9.3/2.0? We need this in order to fix bug 98160 which make people to find it difficult to use RTL languages in international sites such as Facebook.
Hmm, I'm not sure why you refiled this bug though you know bug 166240 (according to bug 98160 comment 17)...
No longer blocks: 98160
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.