www.cendio.com
Bug 5779 - Local cursor doesn't work in IE/Edge or on touch devices
: Local cursor doesn't work in IE/Edge or on touch devices
Status: NEW
: ThinLinc
Web Access
: pre-1.0
: PC Unknown
: P2 Normal
: LowPrio
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2016-01-25 17:29 by
Modified: 2019-04-17 12:26 (History)
Acceptance Criteria:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From cendio 2016-01-25 17:29:24
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.
------- Comment #1 From cendio 2016-01-25 17:32:54 -------
http://caniuse.com/#feat=datauri
------- Comment #2 From cendio 2016-01-25 18:05:51 -------
We currently use the style cursor property, which supports a URI value in all
browsers except for Edge, according to this:

http://caniuse.com/#search=cursor

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?
------- Comment #3 From cendio 2016-01-25 18:09:44 -------
Upstream bug: https://github.com/kanaka/noVNC/issues/572
------- Comment #4 From cendio 2016-01-26 10:02:27 -------
From upstream:
> Here is another couple of relevant links:
>
> https://msdn.microsoft.com/en-us/library/aa358795(v=vs.85).asp 
> http://stackoverflow.com/questions/2636068/hide-cursor-in-chrome-and-ie
>
> 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.
------- Comment #5 From cendio 2019-04-17 12:24:47 -------
This also applies to touch devices.
------- Comment #7 From cendio 2019-04-17 12:26:25 -------
Now fixed upstream in noVNC.