Hi all, I have a website with a login form, but I am experiencing a really strange bug in IE (IE6 on XP, IE7 on XP, and IE7 on Vista). Basically the login form is completely unusable, you can't even click on the input fields at all. It works just fine in Firefox 1.5.0.8/2.0 and Opera 9.02. I even rebuilt the form and it still is unusable. Any suggestions would be appreciated. If you want to see what I am talking about go to: <!-- m --><a class="postlink" href="http://a2zpos.tuscan-art.net/1">http://a2zpos.tuscan-art.net/1</a><!-- m -->) It's fine in IE6-7 on my computer.
2) You should be aware that text/html should not be used with XHTML 1.1; use application/xhtml+xml instead or switch to XHTML 1.0 Strict. IE (as of IE7) doesn't support application/xhtml+xml. Simply changing the <meta> element does not work. This needs to be sent in the actual HTTP Response Header.
Sending XHTML as text/html Considered Harmful (<!-- m --><a class="postlink" href="http://www.hixie.ch/advocacy/xhtml">http://www.hixie.ch/advocacy/xhtml</a><!-- m -->)
Serving up XHTML with the correct MIME type (<!-- m --><a class="postlink" href="http://keystonewebsites.com/articles/mime_type.php">http://keystonewebsites.com/articles/mime_type.php</a><!-- m -->)
<!-- m --><a class="postlink" href="http://www.w3.org/2003/01/xhtml-mimetype/">http://www.w3.org/2003/01/xhtml-mimetype/</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xml.com/pub/a/2003/03/19/dive-into-xml.html">http://www.xml.com/pub/a/2003/03/19/dive-into-xml.html</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.w3.org/TR/xhtml-media-types/#summary">http://www.w3.org/TR/xhtml-media-types/#summary</a><!-- m -->
Content-Typing XHTML (<!-- m --><a class="postlink" href="http://www.greytower.net/archive/articles/xhtmlcontent.html">http://www.greytower.net/archive/articl ... ntent.html</a><!-- m -->)
3) Why are you doing the following?
<li>|</li>
4) I suggest you read these:
The Behavior Layer (<!-- m --><a class="postlink" href="http://www.digital-web.com/articles/the_behavior_layer/">http://www.digital-web.com/articles/the_behavior_layer/</a><!-- m -->)
Separating behavior and structure (<!-- m --><a class="postlink" href="http://www.digital-web.com/articles/separating_behavior_and_structure_2/">http://www.digital-web.com/articles/sep ... ructure_2/</a><!-- m -->)
Behavioral Separation (<!-- m --><a class="postlink" href="http://www.alistapart.com/articles/behavioralseparation/">http://www.alistapart.com/articles/beha ... eparation/</a><!-- m -->)
Unobtrusive JavaScript (<!-- m --><a class="postlink" href="http://www.onlinetools.org/articles/unobtrusivejavascript/">http://www.onlinetools.org/articles/uno ... avascript/</a><!-- m -->)
DOM Scripting - Sample chapter: Best Practices (<!-- m --><a class="postlink" href="http://www.domscripting.com/book/sample/">http://www.domscripting.com/book/sample/</a><!-- m -->)
Accessible DHTML (<!-- m --><a class="postlink" href="http://www.severnsolutions.co.uk/articles/001/">http://www.severnsolutions.co.uk/articles/001/</a><!-- m -->)Thanks for the reply. I know about the content type and all that stuff and I thought it was that and I spent a couple of hours debugging it think that that was the problem. It wasn't. The problem ended up being the AlphaImageLoader filter on IE that basically rendered all of the child elements inside the parent element that had the filter applied, useless. I just specified a JPEG image for IE instead in the CSS and it's all fixed. I was experiencing the same behaviour on another page that had a splash entrance with an image link, and as soon as I removed the filter it worked in IE.
Kind of amusing that the one thing that fixes the PNG support in IE, totally kills the the elements inside parent element.
And I do program for Firefox, (I've been lucky with Opera so far with no problems), and then I apply fixes for IE. Trust me, I know that, I had a week long argument with my employer on that topic before he saw the light of day.They fixed the PNG support in IE7, so you shouldn't need the AlphaImageLoader for it -- just for IE5.5-6.
I've had problems with AlphaImageLoader myself.
So why are you using XHTML 1.1 if you know about the mime-type issue?
P.S. You seem to have paid more attention to my sig than to my 3rd and 4th points.
Oh. That was your sig? Oups, totally read past it. 
I'm using XHTML 1.1 because I want to use the "latest and the greatest". I know that IE doesn't support the "application/xhtml+xml" mime type, but so far I haven't had problems with the display, so I'm just going to stick to it intil I find problems.
I did follow point #3, and removed the "<li>'s".
Actually I think that when you we viewing it you caught it after I had discovered the problem and was reseting everything back to the way it was supposed to be.
As far as #4, I plan on reading the articles, I just don't have time at the moment.
Thanks for the help.You're welcome
I'm using XHTML 1.1 because I want to use the "latest and the greatest". I know that IE doesn't support the "application/xhtml+xml" mime type, but so far I haven't had problems with the display, so I'm just going to stick to it intil I find problems.
You aren't having problems because you are still using text/html.
XHTML 1.1 is not the latest and greatest. Basically it's just a modularized version of XHTML 1.0 Strict. When you serve XHTML as text/html all browsers treat it as HTML, so you get none of the benefits of XHTML. I recommend and typically use HTML 4.01 Strict.
I did follow point #3, and removed the "<li>'s".
So you removed the list instead of fixing it? (Or am I getting your lists mixed up?)
Why are you using inline styles on "ul.nav li"?
Actually I think that when you we viewing it you caught it after I had discovered the problem and was reseting everything back to the way it was supposed to be.
Good chance.
As far as #4, I plan on reading the articles, I just don't have time at the moment.
I've got a list of a few dozen articles I need to read myself.
2) You should be aware that text/html should not be used with XHTML 1.1; use application/xhtml+xml instead or switch to XHTML 1.0 Strict. IE (as of IE7) doesn't support application/xhtml+xml. Simply changing the <meta> element does not work. This needs to be sent in the actual HTTP Response Header.
Sending XHTML as text/html Considered Harmful (<!-- m --><a class="postlink" href="http://www.hixie.ch/advocacy/xhtml">http://www.hixie.ch/advocacy/xhtml</a><!-- m -->)
Serving up XHTML with the correct MIME type (<!-- m --><a class="postlink" href="http://keystonewebsites.com/articles/mime_type.php">http://keystonewebsites.com/articles/mime_type.php</a><!-- m -->)
<!-- m --><a class="postlink" href="http://www.w3.org/2003/01/xhtml-mimetype/">http://www.w3.org/2003/01/xhtml-mimetype/</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xml.com/pub/a/2003/03/19/dive-into-xml.html">http://www.xml.com/pub/a/2003/03/19/dive-into-xml.html</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.w3.org/TR/xhtml-media-types/#summary">http://www.w3.org/TR/xhtml-media-types/#summary</a><!-- m -->
Content-Typing XHTML (<!-- m --><a class="postlink" href="http://www.greytower.net/archive/articles/xhtmlcontent.html">http://www.greytower.net/archive/articl ... ntent.html</a><!-- m -->)
3) Why are you doing the following?
<li>|</li>
4) I suggest you read these:
The Behavior Layer (<!-- m --><a class="postlink" href="http://www.digital-web.com/articles/the_behavior_layer/">http://www.digital-web.com/articles/the_behavior_layer/</a><!-- m -->)
Separating behavior and structure (<!-- m --><a class="postlink" href="http://www.digital-web.com/articles/separating_behavior_and_structure_2/">http://www.digital-web.com/articles/sep ... ructure_2/</a><!-- m -->)
Behavioral Separation (<!-- m --><a class="postlink" href="http://www.alistapart.com/articles/behavioralseparation/">http://www.alistapart.com/articles/beha ... eparation/</a><!-- m -->)
Unobtrusive JavaScript (<!-- m --><a class="postlink" href="http://www.onlinetools.org/articles/unobtrusivejavascript/">http://www.onlinetools.org/articles/uno ... avascript/</a><!-- m -->)
DOM Scripting - Sample chapter: Best Practices (<!-- m --><a class="postlink" href="http://www.domscripting.com/book/sample/">http://www.domscripting.com/book/sample/</a><!-- m -->)
Accessible DHTML (<!-- m --><a class="postlink" href="http://www.severnsolutions.co.uk/articles/001/">http://www.severnsolutions.co.uk/articles/001/</a><!-- m -->)Thanks for the reply. I know about the content type and all that stuff and I thought it was that and I spent a couple of hours debugging it think that that was the problem. It wasn't. The problem ended up being the AlphaImageLoader filter on IE that basically rendered all of the child elements inside the parent element that had the filter applied, useless. I just specified a JPEG image for IE instead in the CSS and it's all fixed. I was experiencing the same behaviour on another page that had a splash entrance with an image link, and as soon as I removed the filter it worked in IE.
Kind of amusing that the one thing that fixes the PNG support in IE, totally kills the the elements inside parent element.
And I do program for Firefox, (I've been lucky with Opera so far with no problems), and then I apply fixes for IE. Trust me, I know that, I had a week long argument with my employer on that topic before he saw the light of day.They fixed the PNG support in IE7, so you shouldn't need the AlphaImageLoader for it -- just for IE5.5-6.
I've had problems with AlphaImageLoader myself.
So why are you using XHTML 1.1 if you know about the mime-type issue?
P.S. You seem to have paid more attention to my sig than to my 3rd and 4th points.
Oh. That was your sig? Oups, totally read past it. I'm using XHTML 1.1 because I want to use the "latest and the greatest". I know that IE doesn't support the "application/xhtml+xml" mime type, but so far I haven't had problems with the display, so I'm just going to stick to it intil I find problems.
I did follow point #3, and removed the "<li>'s".
Actually I think that when you we viewing it you caught it after I had discovered the problem and was reseting everything back to the way it was supposed to be.
As far as #4, I plan on reading the articles, I just don't have time at the moment.
Thanks for the help.
You're welcome I'm using XHTML 1.1 because I want to use the "latest and the greatest". I know that IE doesn't support the "application/xhtml+xml" mime type, but so far I haven't had problems with the display, so I'm just going to stick to it intil I find problems.
You aren't having problems because you are still using text/html.
XHTML 1.1 is not the latest and greatest. Basically it's just a modularized version of XHTML 1.0 Strict. When you serve XHTML as text/html all browsers treat it as HTML, so you get none of the benefits of XHTML. I recommend and typically use HTML 4.01 Strict.
I did follow point #3, and removed the "<li>'s".
So you removed the list instead of fixing it? (Or am I getting your lists mixed up?)
Why are you using inline styles on "ul.nav li"?
Actually I think that when you we viewing it you caught it after I had discovered the problem and was reseting everything back to the way it was supposed to be.
Good chance.
As far as #4, I plan on reading the articles, I just don't have time at the moment.
I've got a list of a few dozen articles I need to read myself.