I've got two questions but as they are different topics completely, I will separate them into two different threads. They kind of relate, but not enough, so here's the first one regarding IE's New JavaScript Blocking Feature: ----------
IE's new content blocking features are wreaking havoc on my methods and designs! For the longest time I've been using the included JavaScript w/ rel="external" (http://www.sitepoint.com/article/standards-compliant-world) method to have links open up new browser windows while keeping the code valid. I know that I've got to use these methods to keep the code valid as standards compliance outlines that you shouldn't opening new content in different windows. BUT! With some of my applications, I'd like to have new windows open while keeping my code valid anyway. The extremely irritating this is, no IE has that lovely content blocker (added in with Service Pack 2) that cause the JavaScript to be blocked. Sure you can just tell it to include the content and off you go but for those that don't know any better, (and trust me, I to Tech Support for an ISP and there are a lot of people that don't know any better), it's a real pain and the chances that your pages will not be rendered properly are too high. Any thoughts? Ideas? Thanks ---------- LAWRENCE CARRIERE [EMAIL PROTECTED] www.lawrencecarriere.com ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
