194183 2019-02-01 19:00:58 -0800 deviceorientation API broken in iOS 12.2 beta 2020-07-08 08:57:04 -0700 1 1 1 Unclassified WebKit WebKit Misc. Safari 12 iPhone / iPad iOS 12 RESOLVED DUPLICATE 195329 InRadar P2 Blocker --- 1 gareth webkit-unassigned bfulgham cdumez ggaren mjs simon.fraser zchrykng oldest_to_newest 1501408 0 gareth 2019-02-01 19:00:58 -0800 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. 1501417 1 zchrykng 2019-02-01 19:57:43 -0800 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? 1501420 2 gareth 2019-02-01 20:04:05 -0800 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. 1501424 3 cdumez 2019-02-01 20:06:22 -0800 <rdar://problem/47584268> 1501985 4 simon.fraser 2019-02-04 13:19:15 -0800 I think you mean <rdar://problem/47645367> 1502007 5 bfulgham 2019-02-04 13:57:32 -0800 We will be pleased to expose a web-facing device motion and orientation permission API once the specification has a proposed interface. 1669628 6 ap 2020-07-07 18:49:28 -0700 > I think you mean <rdar://problem/47645367> It is closed now, should this bug be closed too? 1669759 7 cdumez 2020-07-08 08:57:04 -0700 *** This bug has been marked as a duplicate of bug 195329 ***