{"id":222,"date":"2006-07-17T07:39:27","date_gmt":"2006-07-17T07:39:27","guid":{"rendered":"http:\/\/neosmart.net\/blog\/archives\/222"},"modified":"2013-08-26T18:10:15","modified_gmt":"2013-08-26T23:10:15","slug":"expression-web-designer-and-internet-explorer-think-again","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/expression-web-designer-and-internet-explorer-think-again\/","title":{"rendered":"Expression Web Designer and Internet Explorer? Think Again!"},"content":{"rendered":"

Yeah, you read that right. To re-iterate: if you want to code a site and expect it to load even semi-reasonably in Internet Explorer 6 or 7, you probably don’t want to write it or even touch<\/em> it in Microsoft’s Expression Web Designer<\/a>. At any rate, not this version of Expression.<\/p>\n

Expression Web Designer is very Web 2.0 compatible. It’s the only really big HTML interface that validates directly<\/em> against the W3C standards, by default checking page-display compatiblity against CSS 2.1, instead of against FF, IE6, or something. It does a very good job at that too, but unfortunately, it’s far ahead of Microsoft’s time.<\/p>\n

<\/p>\n

When you write a page in “UTF-8” encoding, Expression Web Designer sometimes takes it to its head to write something called the BOM<\/abbr>, which is a tiny, little, useless unicode character inserted into the code to prove something.<\/p>\n

The only problem is, Internet Explorer 6 & 7 both fall under W3C’s so-called ‘older browsers’ list, and hence, don’t support the BOM at all. What you end up with is Internet Explorer incorrectly displaying php\/ssi includes, and a bunch of unexpected HTML display errors will crop up in Internet Explorer but not any of the other browsers.<\/p>\n

The code with such includes is exactly the same as if it wasn’t<\/em> pieced together server-side, but for the presence<\/a> of this BOM character that skews the code to hell. If you have some weird errors when dealing with server-side includes in Internet Explorer that don’t show up in any other browser on any other platform – this is your man.<\/p>\n

To fix it you have to manually open all pages ‘pieced-together’ by php or whatever SSI you use in Notepad, and then proceed to save them as “ANSI” files instead of unicode.. Then get back to work.<\/p>\n","protected":false},"excerpt":{"rendered":"

Yeah, you read that right. To re-iterate: if you want to code a site and expect it to load even semi-reasonably in Internet Explorer 6 or 7, you probably don’t want to write it or even touch it in Microsoft’s … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[56,69],"class_list":["post-222","post","type-post","status-publish","format-standard","hentry","category-software","tag-bugs","tag-expression-web-designer"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t