Reach consensus on deprecation and removal of de facto standard init*Event() methods about deviceorientation HOT 15 CLOSED

Correction to the above, MDN also lists initEvent() as deprecated.

from deviceorientation.

Trying to figure out who might know about this from code etc. in the various engines:

• EdgeHTML: @adrianba has posted to the list, but I think he's OOO, so perhaps michaelchampion?
• Gecko: @khuey @smaug----?
• WebKit: @cdumez? (also Sam Weinig, but can't find on GitHub)

Between standardization and removal, do y'all have preferences?

from deviceorientation.

@khuey left Mozilla a little while ago to do other fun things

from deviceorientation.

Indeed. Maybe try @bakulf?

from deviceorientation.

Since most engines have it, I'd personally prefer to standardize.

from deviceorientation.

init*Events() are deprecated at least in the sense that new event interface types shouldn't get them, but I don't see any strong reason to remove them if all the implementations support them.

Hmm, though, if we want to make the platform better and eventually remove all the initEvent methods
(and createEvent), then we should try to remove initEvents one by one.

Do we have up-to-date data about initDeviceMotionEvent and initDeviceOrientationEvent usage?

from deviceorientation.

We have these use counters:
https://www.chromestatus.com/metrics/feature/timeline/popularity/865
https://www.chromestatus.com/metrics/feature/timeline/popularity/866

However, despite the fact that I closed #18 I would be perfectly happy to see these standardized, and don't think we can possibly remove all of the init*Event() methods, because:
https://www.chromestatus.com/metrics/feature/timeline/popularity/867

I would, however, like to give them all exactly one required argument as in whatwg/dom#387.

For those that aren't interoperable yet, it's very possible that removing them from n engines could be a faster path to interop than adding them to 4-n, depending on the numbers and usage.

from deviceorientation.

Should also say that if there is one eager individual for each engine, I would support removal as well.

from deviceorientation.

We would love to drop support for it. We are still plumbing Event constructors through for everything, so these won't have that support yet, but we'll get there. Meanwhile, it doesn't matter if no one is programmatically dispatching them in practice anyway.

So +1

from deviceorientation.

@smaug----, given the usage numbers above what do you think?

from deviceorientation.

Dropping them sounds good.

from deviceorientation.

Chrome will be removing these methods.

from deviceorientation.

Closing this issue. Safari Mobile appears to be the only browser still implementing these methods.

from deviceorientation.

I see https://searchfox.org/mozilla-central/source/dom/webidl/DeviceOrientationEvent.webidl#16

from deviceorientation.

Ah, my mistake. I was checking for it in Firefox Developer Tools but obviously flubbed it. Nonetheless, it is marked as deprecated and so I don't think there is any need to keep this issue open in anticipation of specifying these methods.

from deviceorientation.