Cursor glyph for CSS3 'no-drop' is the same as for 'not-allowed'. (spawned off from bug 163174 comment 98) The desired glyph is a hand with a small 'not-allowed' symbol next to it. http://www.worldtimzone.com/mozilla/testcase/css3cursors.html
I've just started working on a new glyph.
Frankly speaking, I edit the corresponding doublebytes manually after creating the cursor. I'll attach the specs for you here, wait a minute.
Created attachment 169054 [details] Windows bitmaps (BMP, ICO, CUR) To save your time, I'll summarize: 0A is X coord offset, 0C is Y coord offset for hotspot.
Created attachment 169055 [details] Microsoft Windows custom cursor (.CUR) for CSS3 no-drop Open it in your favourite hex editor; the first bytes should be: 00 00 02 00 01 00 20 20 04 00 06 00 01 00 E8 02 06 and the following 01 is the hotspot: X=6, Y=1, counting from (0;0) the upper left corner of the bitmap.
Several differences between my version and http://www.gtalbot.org/GRAPHICS/ICO/Custom_made_no-drop.cur are the following: 1) I used 1-pixel white halo around no-drop symbol to make it visible on black or other dark backgrounds 2) I made hand's thumb somewhat wider, to match anatomy of average user
Created attachment 169063 [details] Microsoft Windows custom cursor (.CUR) for CSS3 no-drop Reduced unnecessary bloat; now this cursor is as small in filesize as 326 bytes.
> 1) I used 1-pixel white halo around no-drop symbol to make it visible on black > or other dark backgrounds > Yeah, good idea: MSIE 6 does that. > 2) I made hand's thumb somewhat wider, to match anatomy of average user Also, your .cur file is smaller (766 bytes, 16 colors); mine is 2238 bytes, 256 colors.
2 colors should be enough ;-)
" no-drop Indicates that the dragged item cannot be dropped at the current cursor location. Often rendered as a hand or pointer with a small circle with a line through it. not-allowed Indicates that the requested action will not be carried out. Often rendered as a circle with a line through it. " http://www.w3.org/TR/2004/CR-css3-ui-20040511/#drag-and
A lot of things has changed since 2006, and since I don't have access to a computer with Windows, I wonder, is this still the case?
Should have tried the testcase first, it's the same thing on Mac OS X. This should be switched from a Windows bug to an all OS bug, or, closed, if we feel that there is no need to have different cursors.
What's the right component for this bug?
Hello, I get expected results in https://www.w3.org/TR/css-ui-3/#valdef-cursor-no-drop and http://www.gtalbot.org/DHTMLSection/Cursors.html#CSS3 I get/see an arrow (albeit not a white hand) with a small red 'not-allowed' circle symbol on its righthand side. The spec says: "Often rendered as a hand or pointer with a small circle with a line through it." So, an arrow is fine. I use Firefox 52.0.1 buildID=20170317212642 under Linux 4.8.0-42-generic x86_64 (64bit) Qt: 5.6.1 KDE Plasma: 5.8.5 KDE development platform: 4.14.22 KDE Frameworks: 5.28 Kubuntu 16.10 (codename: yakkety) Can anyone else please report his/her findings for Windows 7, 8, 10 and for Mac OS X 10+ ?
Another 'cursor: no-drop' test: http://test.csswg.org/suites/css-ui-3_dev/nightly-unstable/html/cursor-007.htm
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 "no-drop" is the same as "not-allowed" for me on Win7
Adding ddn so we can update the cursor property page when this is fixed.
(In reply to Chris Mills (Mozilla, MDN editor) [:cmills] from comment #17) > Adding ddn so we can update the cursor property page when this is fixed. hmm, I'm waiting for a fix since 13 years ... btw, why is this marked as "enhancement"? It's just a bug, no?