<html>
<head>
<base href="https://bugs.webkit.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:jono@with.in" title="Jono Brandel <jono@with.in>"> <span class="fn">Jono Brandel</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [Privileged Contexts] Enable opt-in to DeviceOrientation and DeviceMotion for HTTPS-based iframes"
href="https://bugs.webkit.org/show_bug.cgi?id=152299">bug 152299</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>jono@with.in
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Privileged Contexts] Enable opt-in to DeviceOrientation and DeviceMotion for HTTPS-based iframes"
href="https://bugs.webkit.org/show_bug.cgi?id=152299#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Privileged Contexts] Enable opt-in to DeviceOrientation and DeviceMotion for HTTPS-based iframes"
href="https://bugs.webkit.org/show_bug.cgi?id=152299">bug 152299</a>
from <span class="vcard"><a class="email" href="mailto:jono@with.in" title="Jono Brandel <jono@with.in>"> <span class="fn">Jono Brandel</span></a>
</span></b>
<pre>The `allow-device-sensors` has use cases far more integral than advertising purposes. I work at a company where we create, host, and distribute 360 videos, <a href="https://with.in/">https://with.in/</a>. All of our content runs off of a CDN <a href="https://player.with.in/">https://player.with.in/</a>
When we iframe our video player on our site ( e.g: <a href="https://with.in/watch/the-possible-speed-machine/">https://with.in/watch/the-possible-speed-machine/</a> ) we get the CORS cross-domain error because it's a different subdomain. In this case I am the owner of both and feel that the developer has a right to decide which features may trickle down.
Because of the volume of our viewership, it is paramount that we host these massive files on a CDN. Our work around is to offer a touch version for our iOS visitors, whereas visitors on Android get deviceorientation events.
Also, for what it's worth the `allow-device-sensors` is stylistically a similar solution to `allowfullscreen` attributes on iframes.
I hope you'll consider merging Rich's patch into Webkit!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>