User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; ja-JP; rv:1.8b2) Gecko/20050317 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; ja-JP; rv:1.8b2) Gecko/20050317 Firefox/1.0+ In Bug 38447, I commented 'testcase for WinIE doesn't work with latest-trunk'. cbiesinger said: > ------- Additional Comment #156 From Christian Biesinger (:bi) 2005-03-17 05:48 PST [reply] ------- (snip...) >> > Error: Error in parsing value for property 'cursor'. Declaration dropped. > > That error is correct. You always need one of the cursor keywords. See the > grammar at http://www.w3.org/TR/CSS21/ui.html#cursor-props But WinIE doesn't need cursor keywords. This bug is enhancement for IE-compatible. Reproducible: Always Steps to Reproduce:

No, this shouldn't be allowed. Authors should have to provide a portable fallback.

FWIW, most of the sites I tried to test out the fix to bug 38447 do not use a keyword as a portable fallback. Even this "CSS Cursor Tutorial" does not: http://www.echoecho.com/csscursors.htm. I realize that the spec requires a fallback, but this is yet another case where IE decided to ignore the spec and the majority of web developers unfortunately did too as a result. As a portable fallback, couldn't we just use the default cursor for whatever object the cursor style is applied to? In other words, just pretend that the object does not have a cursor style at all. This is exactly what happens now if the keyword is omitted even if the specified cursor can be rendered.

(In reply to comment #3) > As a portable fallback The "portable fallback" is to specify the cursor the spec-compliant way. IE does the right thing with the correct syntax, so authors should be encouraged to use the correct way for the sake of users of browser who follow the spec properly. I filed bug 286840 as a Tech Evangelism bug for this site to correct its documentation. I also filed bug 286835, bug 286836, bug 286837, bug 286838, and bug 286839 for the same issue with other sites. If you find other sites that provide similarly incorrect documentation, please file Tech Evangelism bugs for them and add "[invalid-css-cursor]" to the Status Whiteboard.

*** Bug 313144 has been marked as a duplicate of this bug. ***

(I documented this at http://developer.mozilla.org/en/docs/Using_URL_values_for_the_cursor_property#Compatibility_with_other_browsers)