3 ms·

"I'm getting "Uncaught ReferenceError: Float32Array is not defined" on Chrome on OS X" This error message is not about missing custom method, it's about missin

by bd 16y ago

"I'm getting "Uncaught ReferenceError: Float32Array is not defined" on Chrome on OS X" This error message is not about missing custom method, it's about missing Typed Array data type: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/TypedArray-spec.html https://cvs.khronos.org/svn/repos/registry/trunk/public/webg... All browsers that support WebGL have these data types, older ones can be missing them. "Not working on the latest Chrome or FireFox under XP either." Could you please give us more details (exact browser version, graphics card, eventual error messages / warnings in alerts / console), so that we could figure out where is problem? For example, "latest Chrome" could be latest dev-channel, latest canary or latest Chromium continuous build.

jasonkester 16y ago
Chrome 8.0.552.215 FireFox 3.6.12 Both are out-of-the box, with auto-updates on. So it's pretty much what you'd get if you were a typical user on that browser. It sounds like you're targeting the next crop of as-yet unreleased browsers for your thing. You might want to note that on the demo somewhere, since pretty much nobody but you will be able to make it work right now without downloading a new browser.
- deleted 16y ago
  [deleted]
- bd 16y ago
  "Chrome 8.0.552.215 FireFox 3.6.12" Thanks. This explains it, neither of these browsers does support WebGL. "It sounds like you're targeting the next crop of as-yet unreleased browsers for your thing. You might want to note that on the demo somewhere, since pretty much nobody but you will be able to make it work right now without downloading a new browser." Exactly, you are right. WebGL demos are very much work in progress. They are targeted for browsers which should reach mainstream just sometimes early next year. There is supposed to be an alert about missing WebGL support, but yes, this could be handled in a nicer way. Khronos (WebGL standards body) has some plans for handling this "properly". There is a site where should be "official" explanations and instructions how to get WebGL running: http://get.webgl.org/ http://get.webgl.org/ Idea is that application developers could then just point users to this. Though as this is not ready yet, people resort to own case-by-case solutions.

by bd 16y ago

jasonkester 16y ago

Chrome 8.0.552.215 FireFox 3.6.12 Both are out-of-the box, with auto-updates on. So it's pretty much what you'd get if you were a typical user on that browser. It sounds like you're targeting the next crop of as-yet unreleased browsers for your thing. You might want to note that on the demo somewhere, since pretty much nobody but you will be able to make it work right now without downloading a new browser.

deleted 16y ago
[deleted]
bd 16y ago
"Chrome 8.0.552.215 FireFox 3.6.12" Thanks. This explains it, neither of these browsers does support WebGL. "It sounds like you're targeting the next crop of as-yet unreleased browsers for your thing. You might want to note that on the demo somewhere, since pretty much nobody but you will be able to make it work right now without downloading a new browser." Exactly, you are right. WebGL demos are very much work in progress. They are targeted for browsers which should reach mainstream just sometimes early next year. There is supposed to be an alert about missing WebGL support, but yes, this could be handled in a nicer way. Khronos (WebGL standards body) has some plans for handling this "properly". There is a site where should be "official" explanations and instructions how to get WebGL running: http://get.webgl.org/ http://get.webgl.org/ Idea is that application developers could then just point users to this. Though as this is not ready yet, people resort to own case-by-case solutions.