Live data from Hacker News

Show HN: WebGL Playground

jessevdk.github.io

11–15 of 15 posts

Re: Show HN: WebGL Playground

#13
post #11

Sorry! The WebGL Playground does not support your browser IE 11 here, please remove/fix your browser/feature detection.

The feature detection checks that canvas.getContext("webgl") returns non-null. IE11 does indeed return null for that; it wants "experimental-webgl" instead

The docs mention this also: http://msdn.microsoft.com/en-us/library/ie/dn385811 (second example)

Re: Show HN: WebGL Playground

#14

Are there any potential security implications in providing low level access to OpenGL through a WebGL abstraction? Have there been any exploits in the wild?

The browser is essentially giving user-supplied code (shaders) to a graphics driver that isn't sandboxed in the way the browser's Javascript VM is.

This reason was used by Microsoft [1] and Apple to not implement WebGL in IE and Safari, but I don't know what's changed now.

[1] http://blogs.technet.com/b/srd/archive/2011/06/16/webgl-cons...

Re: Show HN: WebGL Playground

#15
post #11

Sorry! The WebGL Playground does not support your browser IE 11 here, please remove/fix your browser/feature detection.

The feature detection checks that canvas.getContext("webgl") returns non-null. IE11 does indeed return null for that; it wants "experimental-webgl" instead The docs mention this also: http://msdn.microsoft.com/en-us/library/ie/dn385811 (second example)

I meant "IE 11 user here", IE is just one of 3 browsers I use.

Yes, so the site owner should just fix the feature detection (webgl and experimental-webgl) - that's normal.

It used to be best practice to test a website in IE, Firefox and a WebKit based/originated browser (Chrome/Safari). Opening the site with Chrome now shows a dialog that apologize for limited testing, ok.

Post reply on HN