Note that there are some explanatory texts on larger screens.

plurals
  1. POHiding the Cursor in TideSDK
    primarykey
    data
    text
    <p>I'm attempting to work out why some CSS3 cursor options work and some do not in TideSDK desktop applications. Presently, I've determined the following cursor options work:</p> <ul> <li>auto</li> <li>default</li> <li>help</li> <li>pointer</li> <li>progress</li> <li>wait</li> <li>crosshair</li> <li>text</li> <li>vertical-text¹</li> <li>move</li> <li>no-drop</li> <li>not-allowed</li> <li>all-scroll</li> <li>col-resize²</li> <li>row-resize²</li> <li><em>other <code>resize</code> cursors</em></li> <li>-webkit-zoom-in</li> <li><p>-webkit-zoom-out</p> <ol> <li>Does not alias properly (displays black on black)</li> <li>Displays incorrectly (as <code>ns-resize</code> or <code>ew-resize</code>)</li> </ol></li> </ul> <p>The following, however, simply revert to <code>auto</code> or <code>default</code>, depending on the case:</p> <ul> <li>none</li> <li>context-menu¹</li> <li>cell</li> <li>alias</li> <li>copy</li> <li><em>custom <code>url()</code> cursors</em></li> <li>-webkit-zoom-grab</li> <li><p>-webkit-zoom-grabbing</p> <ol> <li>Forgivable, as it is not supported by Webkit</li> </ol></li> </ul> <p>This is quite disturbing for me, as one of the cases I had in mind for my application would require me to hide the cursor. Custom cursors would also be useful for this purpose, as I could set a transparent image as the cursor. However, neither seem to be able to be used.</p> <p>Does anyone have explanation of why a seemingly arbitrary selection of cursors are not supported, or how I might hide the cursor?</p> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload