Last post Jun 24, 2016 07:12 AM by amberly BBW
Feb 19, 2007 12:27 PM|bart n.|LINK
Anybody that has got the menu adapter working with <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">? I need to implement the menu into a masterpage that requires HTML 4.01 (<> XHTML) .
Feb 21, 2007 01:04 PM|Russ Helfand|LINK
Mar 05, 2007 08:40 AM|bart n.|LINK
Mar 05, 2007 02:35 PM|Falcon|LINK
What browser(s) did this occur in?
Also, does it help using the full
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
instead of the shortened version?
My first guess would be that the browser in question is rendering in quirks mode instead of standards mode.
Oct 01, 2007 03:35 PM|Nagash|LINK
Im having a heck of a time getting any CSS to work right since ASP.net 2.0 Insists in rendering tags in XHTML. Any time that happens (HINT: llok at your viewstate form input) browsers will go into quirksmode rendering a lot of your CSS Looking completely
different in IE FF SAFARI.
Oct 01, 2007 05:59 PM|Russ Helfand|LINK
Wow, what a freaky coincidence. I was doing research on this topic myself just a moment ago because I have a since that (for now) must use a DOCTYPE declaring 4.01 HTML and that's causing me some headaches. I'm finding that ASP.NET wants to, for example,
terminate all of my <meta> and <link> tags with closing slashes (like proper XHTML tags)... but is a big no-no in 4.01 HTML's DTD.
Good news: I have read lots and lots of articles, blog entries, forum entries, etc. about this problem. So we are not alone and we are not crazy and we are not missing anything obvious.
Bad news: I really doubt that this can be solved with the simplicity of setting a single configuration switch somewhere. I think we're going to need to tackle this with adapters or something like that.
However... I do have one possible idea...
solve your immediate problem.
Oct 02, 2007 01:27 PM|Nagash|LINK
Ive posted multiple times and no one from MS seems to be able or willing to answer my questions as to how we can can html 4.01 instead of XHTML.
Again MS seems to have gotten thier priorities mixed. WHYin the world would they make asp.net only output XHTML??? I dont understand it it makes no sense.....
But I guess we have to use what they give us since they believe we are NOT able to make our minds up on how to Mark our pages.
I WANT HTML NOT XHTML............
Oct 03, 2007 12:43 AM|Nagash|LINK
wow 914 views and yet no answer......
Oct 03, 2007 02:53 PM|Nagash|LINK
I found the answer.
No mater what you do ASP.NET is hardcoded to spit out XHTML. YOU CANNOT USE REGULAR HTML.....
Isnt that just great!
Oct 04, 2007 02:37 AM|Nagash|LINK
For everyones Future reference.
When coding ASP.net pages NEVER EVER EVER use
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
ONLY XHTML Doctypes
Feb 22, 2008 08:32 AM|that guy|LINK
<link xmlns="http://www.w3.org/1999/xhtml" id="aepref-keyboardnav.enabled" href=""/>
That alone FUBARs rendering of content within Firefox, forces a MIME content-type of application/xhtml+xml rather than a specified text/html within the DTD and renders nothingbut the text of the content page.
Also, is this an issue within the asp.net 3.5 framework?
Feb 27, 2008 07:41 PM|LSW|LINK
I would like to know that too. I am working on a Coldfusion rewrite to C# ASP.NET. Being a standards advocate I hate having to use XHTML.
Go figure. M$ refuses to make IE support XHTML... yet their .NET framework requires XHTML. Isn't that Logical. Guess it looks bad for HTML 5 as well.
Long Live "Tag Soup"
Feb 28, 2008 01:49 AM|MikeJ83|LINK
You are using a non-standard DOCTYPE tag, that is why your dropdown is breaking. If you use the following DOCTYPE tag, your dropdrown will work:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
Jun 24, 2016 07:12 AM|amberly BBW|LINK