The bug in IE with image maps and the statas bar continues with <OPTION>

G

George Hester

Try it. Using Microsoft Internet Explorer 5.5 SP2 (that's the version I am using) in Windows 2000 SP3:

In a html put this in:

<select type="select-one" id="oSel1">
<option value="1" onmouseover="JavaScript:window.status='Hello'; return true;">Hello</option>
<option value="2" onmouseover="JavaScript:window.status='Bye'; return true;">Bye</option>
<option value="3" onmouseover="JavaScript:window.status='Dammit'; return true;">Dammit</option>
</select>

There is no reason to put a onmouseover event in here because it doesn't work. And it should. Any suggestions what I may be doing wrong? Thanks.
 
M

Martin Honnen

George said:
Try it. Using Microsoft Internet Explorer 5.5 SP2 (that's the
version I am using) in Windows 2000 SP3:

In a html put this in:

<select type="select-one" id="oSel1"> <option value="1"
onmouseover="JavaScript:window.status='Hello'; return
true;">Hello</option> <option value="2"
onmouseover="JavaScript:window.status='Bye'; return
true;">Bye</option> <option value="3"
onmouseover="JavaScript:window.status='Dammit'; return
true;">Dammit</option> </select>

There is no reason to put a onmouseover event in here because it
doesn't work. And it should.

IE docs for onmouseover are at
http://msdn.microsoft.com/library/d...author/dhtml/reference/events/onmouseover.asp
And the OPTION element is not listed there as an element to which the
handler/event applies so I don't think MS will consider that a bug.
 
M

Michael Winter

Thanks interesting. It is enabled as an option using FtontPage 2003
intellisense. I guess their intellisense is a little dumb. But you
know the onmouseover and onmouseout events as attributes for the
<OPTION> are listed as available such as here:

http://www.devguru.com/Technologies/html/quickref/html_option.html

That means nothing. The HTML 4.01 Specification lists onmouseover and many
other intrinsic events as attributes of many elements. However, if you've
learnt anything by now, you should be well aware that Microsoft likes to
do their own thing and seem to ignore most standards that they didn't
write themselves*. What is important in this case is that Microsoft don't
support it in their browsers so no number of server-side extensions or
specification quotations will make it work.

Sorry, but that's the way of Microsoft...

Mike

* Gross over-simplification and Microsoft-bashing, but you get the point.
:)
 
G

George Hester

Hi Michael. Yes I get the point. The more I try to use JavaScript for this particular implementation the more I am finding things that should work but don't. I didn't check the MSDN Library for this particular issue because I just ASS-UMED that since it was available in Intellisense in FrontPage 2003, then it was available in Microsoft Internet Explorer. Big Mistake I see.

Oh sure I have much to learn. By trial and error I usually get what I want or change what I want. And in this respect that is what I'll have to do. Change what I want. Change the element; change my mind about using the status bar in this regard. Or leave it in so that if there is some browser out there in browser land then they'll get it. It's set up right (I actually generate these attributes for the <OPTION> dynamically) so at least I learned how to do that with no Client feedback but hey learning.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,764
Messages
2,569,564
Members
45,040
Latest member
papereejit

Latest Threads

Top