RE: [WSG] A quick XHTMLquestion

[Hill, Tim]

Kevin Yank at sitepoint has a great article on this. Although the the target still does not exist, there are no   http://www.sitepoint.com/article/1041     One of his main points:   *--- Quote starts here ---* I mean, if the target attribute of the <a> tag is being phased out, does it really make a difference whether we're setting it with _javascript_ instead of HTML? Sure, the page will validate against the HTML 4.0 Strict and XHTML 1.0 Strict Document Type Definitions, but aren't we technically cheating?   The answer is no. The Document Object Model (DOM), which governs the document objects and attributes that are available to _javascript_ code, is a totally separate standard from (X)HTML. Also consider that the DOM 2.0 standard that was published in January 2003 (well after XHTML 1.0, let alone HTML 4.0) still includes this attribute. It seems clear that while this attribute is slated to be phased out of (X)HTML, it will be available to _javascript_ through the DOM for the foreseeable future.     Tim Hill Computer Associates Graphic Artist tel: +612 9937 0792 fax: +612 9937 0546 [EMAIL PROTECTED] -----Original Message----- From: Ryan Christie [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 1:47 AM To: [EMAIL PROTECTED] Subject: [WSG] A quick XHTMLquestion   I'm trying to move away from XHTML 1.0 Transitional into XHTML 1.1 or 1.0 strict. When I validate my pages as such, it tells me that the target attribute for 'a' tags no longer exists. Would using _javascript_ to open new browser windows on click thrus be acceptable? Is there a better way to achieve this using something other than JS that I'm not aware of?   BTW - my apologies about the Spam Arrest - Peter helped me clear that up ;)       Ryan ---------------------- "Heck with kids - standards are our future." Webmaster, http://www.theward.net