[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Latest Chrome Render to Cubemap bug?

It fix was also merged for Chrome 40 but didn't make the initial release.  It should show up with the first update to Chrome 40.

On Mon Jan 26 2015 at 12:44:35 PM Vangelis Kokkevis <vangelis@google.com> wrote:

You're running into an ANGLE bug that slipped through the release process:


It has been fixed and the fix has been merged to the Chrome 41 branch but unfortunately it missed the Chrome 40 push.


On Mon, Jan 26, 2015 at 9:38 AM, Florian Bösch <pyalot@gmail.com> wrote:
Hi Javi,

I've had some trouble recently with cubemaps in a particular configuration. I did not manage to isolate the issue though, and I don't have a machine that exhibits the problem (it was a clients MBP).

The usual procedure for that kind of thing is:
  1. See if you can find a related conformance test that would fail/succeed in the same way your own code does (https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html)
  2. If a conformance does not exist then isolate the problem and write a minimal test page that exhibits the error
  3. Create a conformance test from that test page (https://github.com/KhronosGroup/WebGL/tree/master/sdk/tests/conformance)
  4. Submit a pull request to that conformance test (https://github.com/KhronosGroup/WebGL/pulls)
  5. Once the pull request is accepted, file tickets with the respective browser vendors. (https://bugzilla.mozilla.org/https://code.google.com/p/chromium/issues/listhttps://bugs.webkit.org/https://connect.microsoft.com/IE/Feedback )