Bugzilla – Bug 5610
Sometimes we don't get a framebuffer update after panning
Last modified: 2017-03-27 14:19:19
You need to
before you can comment on or make changes to this bug.
When panning we require new data from the server to draw the new parts of the
screen. This seems to be working very inconsistently. The result is that you
have blank parts of the screen until you do something else which will trigger
It is a lot easier to reproduce on touch devices, where you don't have a mouse
Upstream bug: https://github.com/kanaka/noVNC/issues/517
Fixed in upstream by double buffering: https://github.com/novnc/noVNC/pull/699
We would no longer need frame buffer updates after panning.
Works as expected