![]() |
|
Welcome to the UndergroundScene Forums forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
ModSword +5 of Editing
Join Date: Mar 2002
Location: Dundee
Posts: 3,337
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Asp.Net anomolies with browsers
Ive just spent about 3 hours trying to find out whats wrong with an asp.net page and the way its rendering elements.
Discovered something weird. When the Asp.Net class is being accessed by the browser it determines which browser its using before generating the HTML code to be rendered by the browser. The upshot is: IE gets HTML 4.0 code everything else gets HTML 3.2 This causes much hilarity with <asp:Panel>'s being converted to <div> in IE and the much loved by Microsoft <table> in everything else. As well as numerous other changes. What makes it even more hilarious are Microsoft dictate adherence to the W3C DOM model as one of the criteria for which vresion of HTML it is sent. From Microsoft, who in IE7 are only getting to grips with fixing this what, 10 years old standard? Info 1 Info 2 |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|