TARGET="_top" in strict HTML ?

[Arthur Connor]

Currently I specified a TARGET attribute inside an <A> tag which is not allowed under strict XHTML.
How do I change the line to meet the requirements of strict HTML?

<A HREF="http://www.targetedoma in.com/" TARGET="_top">. ..</A>

Arty

[Andy Dingley]

On Sun, 4 Jan 2004 14:40:41 +0100, ar***@redseven. com (Arthur Connor)
wrote:

Currently I specified a TARGET attribute inside an <A> tag which is not allowed under strict XHTML.

Use Transitional (or search this ng.)

[Neal]

"Andy Dingley" <di*****@codesm iths.com> wrote in message
news:v6******** *************** *********@4ax.c om...

On Sun, 4 Jan 2004 14:40:41 +0100, ar***@redseven. com (Arthur Connor)
wrote:

Currently I specified a TARGET attribute inside an <A> tag which is not

allowed under strict XHTML.
Use Transitional (or search this ng.)

You know, it's funny. Four posts in a row posted to ciwah and ciwas.
Followups set to ciwas only.

If you're like me, you read ciwah first because it comes first
alphabetically. You see a post with no responses, you reply, not knowing
that umpteen others have also responded. Seems WAY too coincidental to me.
Plus, all 4 posts are on very basic stuff.

Should we be contacting Oliver Stone on this?

[Keith Bowes]

Arthur Connor wrote:

Currently I specified a TARGET attribute inside an <A> tag which is not allowed under strict XHTML.
How do I change the line to meet the requirements of strict HTML?

<A HREF="http://www.targetedoma in.com/" TARGET="_top">. ..</A>

In theory, this should never be a problem. In other words, if you use
frames, then you don't have the ideology of strict (HTML for structure,
CSS for styles, JS for interaction) and if you use strict, you wouldn't
want to ruin it with presentational relics like frames.

If you want to use "target" you should use Transitional. You can also
cheat with JS, but I wouldn't recommend it.

[Jim Royal]

In article <ED************ ***@fe01.usenet server.com>, Keith Bowes
<do****@spam.me > wrote:

If you want to use "target" you should use Transitional. You can also
cheat with JS, but I wouldn't recommend it.

Well then, how should one handle the following hypothetical scenario:

Suppose you have a web site that is pushing data in real time, and you
want to have the browser window refresh periodically. Further suppose
that you have two sets of info that need to refresh at different rates.
For this, you want two browser windows that have been spawned from a
common source, with different meta-fresh values.

Without "target" or Javascript, how do you accomplish this
transparently?

--
Jim Royal
"Understand ing is a three-edged sword"
http://JimRoyal.com

[Stan Brown]

In article <3f************ **********@news .rcn.com> in
comp.infosystem s.www.authoring.stylesheets, Neal wrote:

You know, it's funny. Four posts in a row posted to ciwah and ciwas.
Followups set to ciwas only.

If you're like me, you read ciwah first because it comes first
alphabetically . You see a post with no responses, you reply, not knowing
that umpteen others have also responded. Seems WAY too coincidental to me.

And the four posts are made with four different "From" names. Quite
a coincidence to see this happen four times in short order when I
can't remember it ever happening before.

I think we've been punked.

--
Stan Brown, Oak Road Systems, Cortland County, New York, USA
http://OakRoadSystems.com/
HTML 4.01 spec: http://www.w3.org/TR/html401/
validator: http://validator.w3.org/
CSS 2 spec: http://www.w3.org/TR/REC-CSS2/
2.1 changes: http://www.w3.org/TR/CSS21/changes.html
validator: http://jigsaw.w3.org/css-validator/

[Alan J. Flavell]

[f'ups suggested to a more appropriate group]

On Sun, 4 Jan 2004, Jim Royal wrote:

In article <ED************ ***@fe01.usenet server.com>, Keith Bowes
<do****@spam.me > wrote:

If you want to use "target" you should use Transitional. You can also
cheat with JS, but I wouldn't recommend it.
Well then, how should one handle the following hypothetical scenario:

Suppose you have a web site that is pushing data in real time, and you
want to have the browser window refresh periodically.

HTML Strict doesn't concern itself with such presentation details.
What's a "browser window" when the client agent is a brailler, a
summarising robot, etc. etc.?
Further suppose that you have two sets of info that need to refresh
at different rates. For this, you want two browser windows that have
been spawned from a common source, with different meta-fresh values.
HTML Strict doesn't concern itself with such presentation details.
Without "target" or Javascript, how do you accomplish this
transparently?

Perhaps you're wanting to have too much detailed control over
presentation. Not all client agents present their display using
windows.

But if you don't want what HTML Strict offers, why would you be trying
to use it?

[Nick Kew]

In article <ED************ ***@fe01.usenet server.com>, one of infinite monkeys
at the keyboard of Keith Bowes <do****@spam.me > wrote:

You can also
cheat with JS, but I wouldn't recommend it.

I would very firmly recommend it as second-best to getting rid of the
need for target= altogether. You achieve the same effect for
bells-and-whistles viewers, while leaving users who might have trouble
with it more chance to take control.
--
Nick Kew

[Neal]

"Stan Brown" <th************ @fastmail.fm> wrote in message
news:MP******** *************** *@news.odyssey. net...

And the four posts are made with four different "From" names. Quite a coincidence to see this happen four times in short order when I can't remember it ever happening before.
Different emails too, but the same source in the path.
I think we've been punked.

Indeed.

[Neal]

"Nick Kew" <ni**@fenris.we bthing.com> wrote in message
news:ba******** ***@jarl.webthi ng.com...

In article <ED************ ***@fe01.usenet server.com>, one of infinite monkeys at the keyboard of Keith Bowes <do****@spam.me > wrote:

You can also
cheat with JS, but I wouldn't recommend it.
I would very firmly recommend it as second-best to getting rid

of the need for target= altogether. You achieve the same effect for
bells-and-whistles viewers, while leaving users who might have trouble with it more chance to take control.

You're still going to piss a lot of people off with popups. I
really can't think of a time they're needed aside from trying to
make a buck.

[Neal]

"Jim Dabell" <ji********@jim dabell.com> wrote in message
news:e9******** ************@gi ganews.com...

Neal wrote:
[snip]

You're still going to piss a lot of people off with popups. I
really can't think of a time they're needed aside from trying to make a buck.
I think a lot of people have missed something here:

target="_top" doesn't open a new window. It replaces the top frameset with the new document. Are you thinking of target="_blank" ?

Yes I was. Actually, target="_top" is useful, but allowing it
opens the door for all sorts of abuses and crimes. As it's
disallowed, then we have to educate the public that they can
right-click, open a new page, and trash that frames site. That
technique does away with the need for the target attribute
totally.

Except in framesets, which no right-thinking human likes anyhoo.
;)