New issue
Advanced search Search tips
Starred by 2 users

Issue metadata

Status: Fixed
Closed: Mar 2017
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Launch-OWP
Launch-Accessibility: NA
Launch-Exp-Leadership: ----
Launch-Leadership: ----
Launch-Legal: NA
Launch-M-Approved: 59-Dev
Launch-M-Target: 59-Dev
Launch-Privacy: NA
Launch-Security: NA
Launch-Test: NA
Launch-UI: NA

Blocked on:
issue 651767

issue 674593

Sign in to add a comment

Issue 697598: Deprecate non-standard DeviceOrientation Event initialization functions

Reported by, Mar 1 2017 Project Member

Issue description

Change description:
Remove the DeviceOrientationEvent.initDeviceOrientationEvent and DeviceMotionEvent.initDeviceMotionEvent functions.

Changes to API surface:

 * Remove DeviceOrientationEvent.initDeviceOrientationEvent
 * Remove DeviceMotionEvent.initDeviceMotionEvent

Public standards discussion:

Support in other browsers:
Internet Explorer: Deprecated in Edge
Firefox: Shipped
Safari: Shipped

Comment 1 by, Mar 3 2017

I think this ought to be blocked on shipping the constructors. If it's shipped everywhere, which seems to be the case, I think we should also default to standardizing instead of removing, but is there something extra icky about there init*Event() methods?

Use counters:

That very low usage makes it not unthinkable to remove even though we have interop, but some upside to it would be nice.

Comment 2 by, Mar 3 2017

Clarifying the usage a bit I've found a couple things by searching HTTP Archive which reference these functions:

 * TypeScript has annotations for these functions. Removal will have no effect.
 * Opal (Ruby-to-Javascript transpiler) has bindings for these functions but will attempt to use the constructor first.
 * VR View used to use these functions to generate synthetic DeviceMotionEvents but this code was removed.

Comment 3 by, Mar 3 2017

Blockedon: 651767
Adding the constructor launch bug as a blocker.

Comment 4 by, Mar 3 2017

I'm not sure if this counts as Firefox signaling deprecation but MDN lists initEvent() as deprecated:

It does not document these methods at all.

Comment 5 by, Mar 6 2017

Labels: -M-58 -Launch-M-Target-58-Dev Launch-Legal-NA Launch-M-Target-59-Dev Launch-Security-NA Launch-Test-NA
Summary: Deprecate non-standard DeviceOrientation Event initialization functions (was: Remove non-standard DeviceOrientation Event initialization functions)
foolip@ suggests taking this a bit more slowly so I'm going to change this to a deprecation.

We've missed the M-58 branch point so retargeting for M-59.

Comment 6 by, Mar 9 2017

Blocking: 674593

Comment 7 by, Mar 9 2017

reillyg@, is there no Blink>Foo component that covers this? Of the blocking bugs on issue 674593, this is the only one where I don't know which component to pick. (Doesn't matter since you're working on it, just seems odd.)

Comment 8 by, Mar 17 2017

Project Member
The following revision refers to this bug:

commit 0921e8319f228e406019b434701ac9f181ee8ea1
Author: reillyg <>
Date: Fri Mar 17 19:27:01 2017

Remove non-standard DeviceOrientation Event initializers.

This patch removes DeviceOrientationEvent.initDeviceOrientationEvent
and DeviceMotionEvent.initDeviceMotionEvent and rewrites the LayoutTests
to use the constructors for these objects instead.

BUG= 697598 

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


Comment 9 by, Mar 17 2017

Labels: Launch-M-Approved-59-Dev
Status: Fixed (was: Assigned)
Marking launch approved per LGTMs on the blink-dev Intent to Deprecate and Remove thread:

Comment 10 by, Apr 19 2017

Components: -IO>DeviceOrientation Blink>Sensor

Sign in to add a comment