New issue
Advanced search Search tips

Issue 692709 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 674593


Show other hotlists

Hotlists containing this issue:
Non-Standard-IDL


Sign in to add a comment

Standardize MouseEvent#fromElement and toElement.

Project Member Reported by lunalu@chromium.org, Feb 15 2017

Issue description

They are currently commented as non-standard APIs in Blink, and measured by MouseEvent[From|To]Element.

Currently I don't see those APIs in WebKit or Gecko.
Should we standardize or remove these APIs for interoperability concern? 
 

Comment 1 by tkent@chromium.org, Feb 17 2017

Components: -Blink>DOM>Events Blink>Input
Cc: mustaq@chromium.org dtapu...@chromium.org
Owner: garykac@chromium.org
Status: (was: Untriaged)
There is a spec bug to do just that. https://github.com/w3c/uievents/issues/84

I think the current plan is to spec them but don't know the details.
Cc: foolip@chromium.org
Labels: Hotlist-Interop

Comment 5 by mustaq@chromium.org, Mar 21 2018

Summary: Standardize MouseEvent#fromElement and toElement. (was: Standardize or remove MouseEvent#fromElement and toElement.)
Chrome usage stats looked unbelievably high to me:
  https://www.chromestatus.com/metrics/feature/timeline/popularity/506
  https://www.chromestatus.com/metrics/feature/timeline/popularity/507
so I did a quick look in httparchive.  Looks like there are ~1M pages containing '.fromElement' out of ~14M (in httparchive:har.2018_02_01_chrome_requests_bodies).

I think removal is not an option for us.
This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.
Status: Untriaged
Status: Assigned (was: Untriaged)

Sign in to add a comment