I'm currently implementing Pointer Lock [1] in WebKit, which was
adjusted recently to mimic Fullscreen [2].
The Fullscreen specification calls for events to be dispatched to the
document, but the WebKit implementation dispatches fullscreenchange
and fullscreenerror events to the context element
On Tue, Jun 5, 2012 at 1:06 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jun 4, 2012 at 11:13 PM, Jer Noble jer.no...@apple.com wrote:
Actually, in WebKit, we explicitly also message the document from which the
element was removed in that case. I don't see why this behavior couldn't
I'm currently implementing Pointer Lock [1] in WebKit, which was adjusted
recently to mimic Fullscreen [2].
Why does the Fullscreen specification use an iframe attribute
allowfullscreen to permit/restrict iframe capabilities instead of using
iframe sandbox=allow-fullscreen?
[1]
[correcting Anne van Kesteren's email]
On Tue, Jul 31, 2012 at 3:03 PM, Vincent Scheib sch...@google.com wrote:
I'm currently implementing Pointer Lock [1] in WebKit, which was adjusted
recently to mimic Fullscreen [2].
Why does the Fullscreen specification use an iframe attribute
Thank you Adam, ROC, Anne. I commented on issue.
On Wed, Aug 1, 2012 at 2:05 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, Aug 1, 2012 at 11:04 AM, Anne van Kesteren ann...@annevk.nl
wrote:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17838
I did not want to define new HTML
W3C Web Bluetooth Community Group
http://www.w3.org/community/web-bluetooth/
Use cases Security model, Explainer, and Specification draft
https://github.com/WebBluetoothCG/web-bluetooth
On Wed, Oct 8, 2014 at 12:40 AM, Silvia Pfeiffer silviapfeiff...@gmail.com
wrote:
Indeed, a Web Bluetooth
