Re: New Browser Window Link problem

At 15:36 08/07/02 -0600, Kid Stevens wrote:
<snip/>
>He was asking to solve a target=_blank problem  and target=_anything is
>gone in HTML 4 specs.
<snip/>

Generally, elements and attributes that are deprecated or removed are 
deprecated or removed for a reason. You shouldn't pay lip service to the 
specs by making something that is technically valid but uses client side 
scripting to achieve a deprecated effect.[1] It is _far_ more appropriate 
to use another HTML version with the required behavior built in, or to look 
at completely different ways to solve the problem.

>Popping up stupid little adds is
>rude.  Popping up information is not.

If the information is required by someone who can use pop up windows (for 
whatever reason) then popping up information is rude. It may also be 
something that could land you in court if your website is covered by 
section 508 or similar legislation.

[1] Don't want the alt attribute in images, but want to get a page through 
the W3 validator as XHTML 1.0 strict? Try this:

<script type="text/javascript" src="naughty.js></script>
<script type="text/javascript">noalt();</script>

With this in naughty.js:

function noalt(){
         document.write('<img src="foo.gif" />')
}

This will go through the validator with narry a wimper. _Don't_ use this, 
even if you think it looks like a good idea. Valid pages have to be valid 
before client side script processing as well as after.

This isn't quite the same as using JavaScript to `solve' the target 
problem, but it is still in the same ballpark.

Andrew

--
http://aamcf.co.uk/

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA