WingNews logo WingNews GitHub [2]
top | item 4873605

WebGL: Pointer Lock and First Person Shooter Controls

37 points| arasmussen | 13 years ago |html5rocks.com | reply

13 comments

order
[+] jrabone|13 years ago|reply
Hmm. Enabling this for any element regardless of full-screen state might be a bad idea. Is the warning popup modal? Can you use it to cause the user to click on something other than the intended target by intentionally drawing the pointer in the wrong place?

Like JavaScript, this needs a default-disable, on for trusted sites only mode.

[+] arasmussen|13 years ago|reply
I don't see why this is really a security issue. You can't control their pointer, it just becomes disabled. The popup and the pointer lock are managed by the browser, so you can't trick them into doing anything and they can always get out of it by just pressing escape.

Seems pretty solid to me.

[+] Tmmrn|13 years ago|reply
Well, chromium pops up a bar on the top with buttons for denying or accepting the request of the website to disable the cursor before it does anything.
[+] dazzawazza|13 years ago|reply
Thanks for posting this. I develop games and I've always dismissed the browser for making games because I was ignorant of this API.

Now when all browsers support it I will look more closely.

Thanks.

[+] MattDL|13 years ago|reply
Was just looking at the Quake 3 demo and noticed the FPS was locked to 60. Wondering if this is a limitation of the demo or of the browser (FF nightly in my case).

If so that may turn out to be a bit short sighted in the long term.

[+] dcpn|13 years ago|reply
Running 100+ FPS here (Chrome)
[+] SafeSituation|13 years ago|reply
I'm running Firefox 17.0.1 on Ubuntu 12.04.1 and I don't seem to be able to get any of the demos working. Anyone have a fix?
[+] misleading_name|13 years ago|reply
Same here, but chrome works. I'm not sure it's a point lock issues, since that's supposed to work on FF.

In console, the difference I noticed is that FF has this error: Firefox can't establish a connection to the server at ws://./. - shoote...tBqO.js (line 57)

Chrome doesn't have that error.

[+] arasmussen|13 years ago|reply
What specifically doesn't work? Do they not render (WebGL issue) or does your pointer not get locked (Pointer Lock issue)? Try googling "firefox pointer lock doesn't work", I'm sure something relevant will come up.