|
|
Of Safari, Sainsbury's and style sheets [UK]
This brings up a question that I have been asked in the past. Maybe you could shed some light on, or direct me in the right direction. Why does css show up differently on win ie vs mozilla/khtml browsers and shouldn't this be something the mozilla/khtml should include for compatibility with win ie? I could see the view point that one would not want to implement non-complaint code as it would just encourage developers to produce bad code. What is it one has to do to make sure their css is compatible on both win ie and mozilla/khtml browsers?
Of Safari, Sainsbury's and style sheets [UK]
The problem is not necessarily with Mozilla browsers. The problem is in fact with IE. IE has a lot of CSS rendering bugs which have been around since versions 5/5.5. IE in some cases does not render CSS according to the standard defined by the W3C. The answer to this is not to have Mozilla acknowledge bad rendering in IE as "good", and employ those rendering bugs in it's browser. The answer is that IE should correct it's rendering engine to function properly with the CSS standard.
Of Safari, Sainsbury's and style sheets [UK]
This is broadly true, but it's worth pointing out that the box model rendering problems have been corrected in IE6. However it's not that simple, unfortunately. In order to get IE6 to render the box model correctly HTML pages need to have the correct document type. If they don't, then IE6 reverts to quirks mode, which means it uses the old, incorrect box model rendering. And there's more! Even if the HTML page contains the correct document type, IE will still revert to quirks mode if that page also contains an XML declaration. All this and much more is described in all the gory details at www.alistapart.com |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.30 seconds |
|