Bugzilla – Bug 5779
Local cursor doesn't work in IE/Edge or on touch devices
Last modified: 2019-05-31 14:34:52
You need to
before you can comment on or make changes to this bug.
Normally we use a data uri to give the canvas a custom cursor. However, this
isn't supported in any version of Internet Explorer or Microsoft Edge. This
results in a forced server side cursor (see bug 5148).
We should investigate other ways of providing a local cursor in the HTML5
client for IE and Edge.
We currently use the style cursor property, which supports a URI value in all
browsers except for Edge, according to this:
The problem is that the cursor sent from the server is stored in a Data URI,
which isn't supported. Could we perhaps try to, from the server, present the
url of the cursor?
Upstream bug: https://github.com/kanaka/noVNC/issues/572
> Here is another couple of relevant links:
> Unfortunately, it doesn't seem that IE/Edge are going to support either data
> URIs or the "none" option to hide the cursor. One option we could explore is
> the PointerLock API which would allow us to hide the cursor and then render our
> own directly in the canvas. However the downside is that the captures the
> pointer inside the canvas and it requires user permission.
> Probably the best option that would work everywhere (all browsers and older
> versions too) would be to change the cursor to a blank cursor file and then
> directly render the mouse in the canvas. It's not as nice as just having the
> browser to the work of rendering the cursor for us, but it's the best option I
> can think of for supporting this widely if we think it's important.
This also applies to touch devices.
Now fixed upstream in noVNC.