Re: [WSG] TARGET in 4.01 Strict

[Mike at Green-Beast.com]

Hello Stephen,   Don't apologize for being blunt. If that's how you want to write your sentiments it's fine by me. No offense taken.   For the record, I'm not saying hiding the target attribute in a script element is standards compliant, and I don't open new windows on any of my sites. None. I was just trying to answer the fellow's question with yet another alternative that functions and doesn't set off the validator (plus facilitates keyboard users). Others had already supplied window.open.   My only personal use of this is in my CMS [1] so that users can open the documentation library while in mid-edit without fear of losing their work. This is known in advance by CMS users if they read the documentation supplied before downloading and using the product. I also offer a setting in the CMS that users can choose if they want their site to open in a new window if launched from within the CMS.   [1] http://greenbeastcms.com/   Sincerely, Mike Cherim http://green-beast.com/ http://accessites.org/     [pony mode] ?¿? This seems a little ridiculous to me.  Just because a page/site,  passes the automated W3C test, does not make it standards compliant.   Tricking the validator into thinking that you are serving valid  <regex>X?HTML[1:5]</regex> while breaking it using _javascript_ to  insert non-standard code completely undermines the whole self- accreditation process.  This is as bad as using your Web server to  present clean versions of your page to the validator while serving  bad pages to your users. [/pony mode] Ok that might of been a bit blunt but... why not use window.open('') as a standard behavior OR just include  the target property in the HTML, I don't think you'll break any  browser by doing this and you will be able to settle with your  conscience that you're not being underhand about using non-standard  HTML. Stephen