4 replies to this topic

[zeroradius]

Hey guys,
Just started my first asp.net class. I decided to put a little (crappy) design to my pages so that I do not have to look at a white form the entire time I code. My proffesor told me in class today that the CLR will make it so that my page runs corectly under all browsers. I used proper XHTML just to be safe but my page still only loads corectly in FireFox while IE destroys it. So my question is: What can I do to make my asp.net page design load corectly in all browsers?

Attached is the page rendered in the two browsers:



Edit: It is now working. I did not change anything, I went to render it in IE to show my mom why I was not working on it and it started working. ....... I am now extremely confused, but at least it is working!

Attached Files

•  myPageFf.jpg   45.87K   22 downloads
•  myPageIE.jpg   41.33K   33 downloads

Edited by zeroradius, 01 November 2008 - 03:55 PM.

[TkTech]

The irony that your code initially works better in a Mozilla product vs a Microsoft product is hilarious.

Every browser renders elements and blocks in different ways. Designing a complete site that works right off the bat with all of them is a near impossibility. Even CC took a lot of work to get everything working on most common browsers.

Also, CLR = Common Language Runtime. Please tell me that was your interpretation and not word-for-word what your professor said. The CLR has absolutely nothing to do with how its rendered.

[WingedPanther]

Also, be aware that IE6 and IE7 render pages differently. IE7 significantly improved it's CSS support. As it is, one of the bugs in one of my applications is that IE7 adds a gap between my menu and instructions. I've determined this happens when the instructions are inside the form tag instead of in front of it. Why a <form...> should create a blank line is beyond me.

[zeroradius]

Well my interpretation was that the CLR took code written in the .net frame work and compiled it into machine code. And adjusted the compiled code to work on multipule browsers so that you do not have to re-write your application for each type of browser. I know it is a type of virtual machine because my proffesor compared it to JVM but again he gave the same explantation. I have not taken the time to acualy look it up because my proffesor is usualy right. I may have misheard him i guess :o

[WingedPanther]

The CLR will take what you have written and server of the HTML to the browser. How that HTML is rendered by the browser is determined by the browser. The CLR does not necessarily know what browser it is serving to, how it renders code, or how you intend for the code to be rendered.