[wp-hackers] XHTML Strict compliant replacement for target=_new
geoff at zorched.net
Fri Oct 21 18:38:07 GMT 2005
That method is interesting. It also lead me to read about XHTML and
DOM and realized (although I sort of knew this I think) that those
specs are completely independent. So, while target is invalid XHTML
(Strict) it's valid DOM . . . sort of weird? :)
really concerned. It's no different functionally than hardcoding
'_new' in the target because they both have a consistent defined
In the end, I guess what I was trying to provide was another
automated option so that individuals wouldn't have to customize their
install in code (which makes upgrades harder of course). Part of this
is a philosophical question about the goals of WordPress in terms of
how much to automate vs. how much to leave up to the individual to do
on their own.
It would be fairly easy to code up a query to determine if the 'rel'
the header. So, you could completely automate that version as well.
Thoughts on this? What if we provided all 3 options and let the user
choose? Does that make it way to complicated? Is it worth the effort?
On Oct 20, 2005, at 9:08 PM, Jeff Minard wrote:
> Luc Saint-Elie wrote:
>> I use rel="external"
>> and a JS bit of code
> That gets my vote over baked in JS.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
Geoff Lane <geoff at zorched.net>
More information about the wp-hackers