Bug 101286
Summary: | WebGLCanvas contents are not updated correctly. | ||
---|---|---|---|
Product: | WebKit | Reporter: | Kalyan <kalyan.kondapally> |
Component: | WebKit EFL | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | igor.oliveira, kangil.han, laszlo.gombos, lucas.de.marchi, ostap73, ryuan.choi, tonikitoo, yael, zeno |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Linux | ||
Bug Depends on: | 101291 | ||
Bug Blocks: | 102991 |
Kalyan
Try running the following webgl demo in MiniBrowser: https://www.khronos.org/registry/webgl/sdk/demos/webkit/WebGL+CSS.html
Some of the textures are not rendered properly.
Mesa error log shows the following error:
Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glBlitFramebufferEXT(incomplete draw/read buffers)
Demo works fine on all other browsers.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Kalyan
Working on a patch
Zeno Albisser
(In reply to comment #1)
> Working on a patch
I assume that you are missing the BlitFramebuffer extension.
In this case the solution is actually drawing the texture using the appropriate shaders.
Take a look at GraphicsSurfaceWin.cpp function GraphicsSurfacePrivate::drawTexture.
Kalyan
(In reply to comment #2)
> (In reply to comment #1)
> > Working on a patch
>
> I assume that you are missing the BlitFramebuffer extension.
> In this case the solution is actually drawing the texture using the appropriate shaders.
> Take a look at GraphicsSurfaceWin.cpp function GraphicsSurfacePrivate::drawTexture.
The error can also be caused in case FBO has no valid read/write buffers when trying to perform operations like blitting
Kalyan
This issue got fixed with the changes done in 101291.
Ryuan Choi
I removed [EFL] alias not to redirect this bug when we searched [EFL]
Kalyan
(In reply to comment #5)
> I removed [EFL] alias not to redirect this bug when we searched [EFL]
This bug is specific to EFL port, the alias does make sense here.
Any specific reason why we don’t want it ??
Kangil Han
(In reply to comment #6)
> (In reply to comment #5)
> > I removed [EFL] alias not to redirect this bug when we searched [EFL]
>
> This bug is specific to EFL port, the alias does make sense here.
>
> Any specific reason why we don’t want it ??
Oh, now searching with '[EFL]' displays result well in bugzilla!
@kalyan : IIRC, search result with '[EFL]' always redirects here. :)