New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 568261 link

Starred by 8 users

Issue metadata

Status: Fixed
Email to this user bounced
Closed: Feb 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----

Blocked on:
issue 263308

issue 568218

Sign in to add a comment

Remove or un-deprecate KeyboardEvent.keyLocation

Project Member Reported by, Dec 9 2015

Issue description

KeyboardEvent.keyLocation was deprecated in  issue 263308 .  Usage counters are high, but we know they're unreliable because of the prevalence of event copying code.

We should either remove keyLocation entirely (to match the spec), or concede that it's required for compat and undeprecate (and perhaps specify) it.

I think we should probably just do an httparchive search and if we fail to find any top sites that really depend on this API, we should try removing it.

Anyone cc'd want to pick this up?

Blocking: chromium:568218

Comment 3 by, Dec 11 2015

I've done a rather exhaustive analysis of hits in the 20150101 httparchive data, and based on that I'm pretty confident we could remove this. Amusingly enough, a lot of the hits were for people copying events but blacklisting this attribute simply to avoid the deprecation message.

I suggest that we remove this early after the next branch point and see how it goes.

Comment 4 by, Dec 14 2015

Status: Assigned
Preparing an Intent to Remove now.
Project Member

Comment 6 by, Feb 17 2016

The following revision refers to this bug:

commit 263d94f9b2dc4a0a3cf5b3124c1cc8d2163a4410
Author: philipj <>
Date: Wed Feb 17 02:13:49 2016

Remove KeyboardEvent.prototype.keyLocation (alias of location)

Intent to Remove:

BUG= 568261 

Review URL:

Cr-Commit-Position: refs/heads/master@{#375759}


Comment 7 by, Feb 17 2016

Status: Fixed

Sign in to add a comment