Sent by Jukka K. Korpela on 28 March 2004 15:03
On Sun, 28 Mar 2004, Rafael B. wrote:
> As the xhtml 1.1 strickt doesn=B4t admit
>
> target=3D"_blank"
>
> I am using to open new pages the golem one which validates,
This isn't particularly related to the topic of this list, which is the
practical use of CSS. Opening new windows _might_ be regarded as a job for
CSS, but there is currently no way to do such things in CSS.
However, some of the assumed solution _may_ have an impact on CSS.
> you can find
> the page where I=B4ve got it from here:
>
> http://www.zeldman.com/daily/0503a.shtml#strictlyspeaking
Sorry, but it is seriously misguided. It says: "If you want the target=3D""
attribute in XHTML 1.1, all you need is the right DTD." That makes no
sense. If you add something to XHTML 1.1, it's no XHTML 1.1 any more.
You could just as well say "If you want the <dwim> element in XHTML 1.1,
all you need is the right DTD."
If you wish to use the target=3D"..." attribute, just use HTML 4.01
Transitional or, if you wish to use XHTML for some odd reason,
XHTML 1.0 Transitional. Simple as that.
But the CSS impact of the misguided approach is that once you use
a doctype declaration that is none of those defined in the HTML
specifications, you enter a dark zone in the doctype sniffing game.
The document you cite actually mentions this, and ends with the statement
"Rather than open these multiple cans of worms, we still advise designers
who want to open new windows via the target attribute to use XHTML 1.0
Transitional."
The problem with doctype sniffing is that you really cannot know how
different browsers will (mis)treat your document depending on the exact
form of the doctype declaration (or its absence). Various documents on
this have been written, but both the exact conditions of triggering
"standards" and "quirks" modes and the exact effects on dealing with CSS
(and, to a lesser degree, with HTML) across browsers are more or less
unknown. This is bad enough, and there's no reason to make things even
worse by inventing new doctype declarations _only_ for the purpose of
being able to use a transitional feature from HTML 4 and XHTML 1.0 and
still pretend to be using XHTML 1.1.
In fact, for as consistent processing of your style sheets as possible,
the safest way would be to start each of your documents with
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
if you want "standards" mode and use no doctype if you want
"quirks" mode, no matter what the actual markup is. This would imply that
in validation you would need to use a modified copy of the document or
use "doctype override" if possible, unless you really meant to use
HTML 4.01 Strict.
--=20
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/