RESOLVED DUPLICATE of bug 195329 194183
deviceorientation API broken in iOS 12.2 beta 
https://bugs.webkit.org/show_bug.cgi?id=194183
Summary deviceorientation API broken in iOS 12.2 beta
Gareth Morgan
Reported 2019-02-01 19:00:58 PST
The Web Standard deviceorientation API is broken in iOS 12.2 beta. The feature has reverted to being disabled, which breaks all the websites (including ours) which rely on this part of the web standard. I realize there are some privacy issues, and discussion WRT adding a permission pop-up for this feature. But having the feature disabled is unacceptable.
Attachments
Add attachment proposed patch, testcase, etc.
Zachary King
Comment 1 2019-02-01 19:57:43 PST
Personally, I don't see this as a bug. Unless there is a mechanism in place to request permission from the user it should be disabled by default. Either way, WebKit itself is working as designed, shouldn't this be more of a "bug", for lack of a better word, against Safari/iOS's default settings?
Gareth Morgan
Comment 2 2019-02-01 20:04:05 PST
It's a regression where an established part of the web standard, that is in use by many websites, and was working fine prior to 1.22b, is not longer functioning as defined in the web standard. Additionally, in the discussion in the WC3 discussion on this matter (https://github.com/w3c/deviceorientation/issues/57) I was informed that the Webkit bug database was the correct place to flag this bug.
Chris Dumez
Comment 3 2019-02-01 20:06:22 PST
<rdar://problem/47584268>
Simon Fraser (smfr)
Comment 4 2019-02-04 13:19:15 PST
I think you mean <rdar://problem/47645367>
Brent Fulgham
Comment 5 2019-02-04 13:57:32 PST
We will be pleased to expose a web-facing device motion and orientation permission API once the specification has a proposed interface.
Alexey Proskuryakov
Comment 6 2020-07-07 18:49:28 PDT
> I think you mean <rdar://problem/47645367> It is closed now, should this bug be closed too?
Chris Dumez
Comment 7 2020-07-08 08:57:04 PDT
*** This bug has been marked as a duplicate of bug 195329 ***
Note You need to log in before you can comment on or make changes to this bug.