W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2007

[whatwg] Target Attribute Values

From: Charles Iliya Krempeaux <supercanadian@gmail.com>
Date: Fri, 27 Apr 2007 00:38:36 -0700
Message-ID: <84ce626f0704270038i1521b394x22093e14801e7ba9@mail.gmail.com>

Here's one use case....

In the online advertising business, ads are usually put in <iframe>s
for security reasons.  (So the ad can't tell what page it's on... get
user cookies from that domain... etc.)

So... if you didn't use a "_blank" for the target, the landing page
for the ad would open up in the tiny <iframe> (instead of a new

See ya

On 4/26/07, Lachlan Hunt <lachlan.hunt at lachy.id.au> wrote:
> Hi,
>    This is regarding the valid browsing context names, used for the
> target attribute [1].
> Why is _blank still considered a conforming value?  On IRC, Hixie
> mentioned that there are some legitimate use cases, but didn't list any.
>   I've argued against popups many times before and heard many arguments
> for them, but I'm yet to hear of any legitimate use cases.  If there are
> any, what are they?
> _new is also not specced, yet it is widely used and treated as a magic
> value like _blank in Firefox.  Maybe it should be specced the same as
> _blank.  However, IE, Opera and Safari didn't appear to treat it as
> such, so maybe it's not needed.
> http://www.whatwg.org/specs/web-apps/current-work/#valid8
> --
> Lachlan Hunt
> http://lachy.id.au/

    Charles Iliya Krempeaux, B.Sc.

    charles @ reptile.ca
    supercanadian @ gmail.com

    developer weblog: http://ChangeLog.ca/
Received on Friday, 27 April 2007 00:38:36 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:54 UTC