<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [WebGL Conformance] clipping work incorrectly on y-axis" href="https://bugs.freedesktop.org/show_bug.cgi?id=111247#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [WebGL Conformance] clipping work incorrectly on y-axis" href="https://bugs.freedesktop.org/show_bug.cgi?id=111247">bug 111247</a> from <a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> Tapani Pälli</a> <pre>(In reply to Fritz Koenig from <a href="show_bug.cgi?id=111247#c9">comment #9</a>) > I see a few issues in this bug. I dug into the clipping issue as it applies > to GL_MESA_framebuffer_flip_y in > (<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=964010#c22">https://bugs.chromium.org/p/chromium/issues/detail?id=964010#c22</a>) > > My takeaway was that Mesa was performing differently with system > framebuffers and user framebuffers. GL_MESA_framebuffer_flip_y allows the > user framebuffer to follow the path of the system framebuffer and therefore > come out upside down. > But, according to the spec they are both correct because of the diamond > exit rule. > > I'm also a little confused how this is affecting FF. Chromium is using the > extension for GLES. Is FF also using the extension? Or did enabling this > extension change the functionality of Mesa when the extension did not > enabled? Independent of what's going on with FF, this bug is easy to reproduce with chrome. I noticed that the subtest starts to pass if I disable GL_MESA_framebuffer_flip_y extension in i965 driver, maybe chrome does something wrong when the extension is enabled?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>