[wp-hackers] XHTML Strict compliant replacement for target=_new

Amit Gupta wp at igeek.info
Sat Oct 22 17:58:08 GMT 2005

Jason Bainbridge <jbainbridge at gmail.com> wrote:
|  Err "or if it must stay then implementing the alternative
|  rel="external" solution posted in a later post." so I was saying if
|  the target=_new had to stay then I would vote for that solution. :)
|  Sorry about the confusion.

no problem. also, someone raised the issue to not fiddle with
standards & that they didn't mean validating the data & then
manipulating it via DOM by adding the "target" attribute. so the
function that I gave should satisfy him as well, as using "onclick"
event handler is perfectly within standards & so is using the
javascript "window.open". :)

Amit Gupta
http://igeek.info/  ||  http://blog.igeek.info/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://comox.textdrive.com/pipermail/wp-hackers/attachments/20051022/7df8f1ba/attachment.htm

More information about the wp-hackers mailing list