 | |
Re: cursor
Macromedia Dreamweaver Macromedia Dreamweaver Discussions (macromedia.dreamweaver)
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: cursor -
11-01-2004
, 04:04 AM
#2
| |||
| |||
|
|
The "cursor: hand; " is an IE only style, that is not in the definition of CSS. Use only the cursor: pointer;, this works fine in IE and Mozilla both. I'm not sure about Opera though. |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Originally posted by: Did you read the link I posted near the top of this thread? Are they wrong <BR>when they say:<BR>"<BR>pointer: Explorer 6 Windows, Mozilla, Opera, Explorer 5 Mac, Safari 1.0+<BR><BR>hand: Explorer 4-6 Windows, Opera, Explorer 5 Mac, Safari 1.2<BR><BR>The cross-browser code does not work in Safari 1.0. 1.2 has no problems."<BR><BR>?<BR><BR>I just took their word for it. Actually they are not wrong, but just because it works, doesn't mean it's right  There is no cursor: hand; in the CSS definition and if Youwant to create _valid_ HTML/CSS, You have to do it the W3C way , not the MS way. http://www.w3.org/TR/CSS21/ui.html#propdef-cursor |
#5
| |||
| |||
|
|
Hi again, I'm all for validation, but draw the line when it cheapens the users experience. If there are browsers out there that will not respond to pointer, but will hand, then I'm writing invalid code to accommodate the poor browser support for the standards. We don't make the browsers, but have to work with them when our target is using them, right? If I'm understanding the advice on that url I supplied, the pointer cursor declaration, however valid, won't work for sub version 6 IE. Is that right? If that's the case then it will be another IE version before I at least might feel comfortable dropping the hand declaration to make valid code. If that's not the case, and all the browsers will support pointer, then I'll happily loose hand. I only have FF and IE6 on PC. Is there anyone with a sub 6 IE or other versions or Mac that can advise if pointer alone doesn't work and if so, if adding hand makes it work? Tks, Lossed "kreatiivne" <webforumsuser (AT) macromedia (DOT) com> wrote in message news:cm52rc$fiu$1 (AT) forums (DOT) macromedia.com... Originally posted by: Did you read the link I posted near the top of this thread? Are they wrong <BR>when they say:<BR>"<BR>pointer: Explorer 6 Windows, Mozilla, Opera, Explorer 5 Mac, Safari 1.0+<BR><BR>hand: Explorer 4-6 Windows, Opera, Explorer 5 Mac, Safari 1.2<BR><BR>The cross-browser code does not work in Safari 1.0. 1.2 has no problems."<BR><BR>?<BR><BR>I just took their word for it. Actually they are not wrong, but just because it works, doesn't mean it's right There is no cursor: hand; in the CSS definition and if Youwant to create _valid_ HTML/CSS, You have to do it the W3C way , not the MS way. http://www.w3.org/TR/CSS21/ui.html#propdef-cursor |
#6
| |||
| |||
|
|
As I said earlier, if you are getting the wrong pointer, it's usually because you have mismanaged your code. A good example would be applying behaviors directly to <img> tags, e.g., img src="images/na334.gif" width="334" height="334" border="0" onClick="MM_popupMsg('Boo')" This image will not show a pointer in either NN or IE6, but this one will - a href="javascript:;"><img src="images/na334.gif" width="334" height="334" border="0" onClick="MM_popupMsg('Boo')"></a The difference is that I a) set my Events for list to v4+ browsers as I should, and b) used <A> onClick for my event. -- Murray --- ICQ 71997575 Team Macromedia Volunteer for Dreamweaver (If you *MUST* email me, don't LAUGH when you do so!) ================== http://www.dreamweavermx-templates.com - Template Triage! http://www.projectseven.com/go - DW FAQs, Tutorials & Resources http://www.dwfaq.com - DW FAQs, Tutorials & Resources http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes ================== "Lossed" <blankemail (AT) hotmail (DOT) com> wrote in message news:cm591m$n1s$1 (AT) forums (DOT) macromedia.com... Hi again, I'm all for validation, but draw the line when it cheapens the users experience. If there are browsers out there that will not respond to pointer, but will hand, then I'm writing invalid code to accommodate the poor browser support for the standards. We don't make the browsers, but have to work with them when our target is using them, right? If I'm understanding the advice on that url I supplied, the pointer cursor declaration, however valid, won't work for sub version 6 IE. Is that right? If that's the case then it will be another IE version before I at least might feel comfortable dropping the hand declaration to make valid code. If that's not the case, and all the browsers will support pointer, then I'll happily loose hand. I only have FF and IE6 on PC. Is there anyone with a sub 6 IE or other versions or Mac that can advise if pointer alone doesn't work and if so, if adding hand makes it work? Tks, Lossed "kreatiivne" <webforumsuser (AT) macromedia (DOT) com> wrote in message news:cm52rc$fiu$1 (AT) forums (DOT) macromedia.com... Originally posted by: Did you read the link I posted near the top of this thread? Are they wrong <BR>when they say:<BR>"<BR>pointer: Explorer 6 Windows, Mozilla, Opera, Explorer 5 Mac, Safari 1.0+<BR><BR>hand: Explorer 4-6 Windows, Opera, Explorer 5 Mac, Safari 1.2<BR><BR>The cross-browser code does not work in Safari 1.0. 1.2 has no problems."<BR><BR>?<BR><BR>I just took their word for it. Actually they are not wrong, but just because it works, doesn't mean it's right There is no cursor: hand; in the CSS definition and if Youwant to create _valid_ HTML/CSS, You have to do it the W3C way , not the MS way. http://www.w3.org/TR/CSS21/ui.html#propdef-cursor |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.