css3 implementation / link presentation

css3 implementation in browsers, use of target attribute

[zarforpar]

Hello,

I'm wondering about using the target-name and target-new properties in the css3 draft document (from 2004, which seems to be current), and if it's still not supported enough to implement.

I don't feel great about doing target="_blank" anymore, but maybe I just need to talk to my therapist about that.

Opinions? Facts?

[SuzyUK]

hi zarforpar

although the CSS3 documents for the CSS3 Hyperlink Presentation Module [w3.org] are online, this is part of the CSS-WG's new move to make their work public, they are DRAFT which means they are subject to change. It also means, that they could be, or already are, implemented by some of the browsers, but the only way to find out (for now) is to find a test suite which covers this particular module.

short answer: I'm pretty sure it's not supported enough to rely on

talk to your therapist, and tell him or her it you might be needing their services for a wee while yet.. at least while you're using target="_blank" - which IMHO if you need to do and it works, then do it ;)

[zarforpar]

Ok thanks,

even though it doesn't seem quite right. As for the draft status of that proposal - how long will/does it stay that way? I was thinking three plus years is a long draft period. Maybe this is not the forum for that thought.

Will stay the course with target blank. Cheers.

[SuzyUK]

how long will/does it stay that way? I was thinking three plus years is a long draft period. Maybe this is not the forum for that thought.

yes this is the right forum, and the answer is how long is a piece of string.. seriously though you're right 3+ years is much too long hence the frustration of some when "standards" are mentioned

On the + side there does appear to be some to movement towards CSS3 very recently - there's been a bit of a standoff with IE for the last 6-7 years. The date on that particular CSS3 draft is when it was started on I would imagine. Some CSS3 properties have already been implemented by the likes of FF. Opera and Safari and all we need now is for IE8 to pick up their game and start back implementing new things.

On the - side, something like this (which has accessibility repercussions) will be slow to be taken up because versions of IE7 and below will never support it and their users are, and will be for a long time, in the majority, Developers, who do want to do the right thing for recommended accessibility guidelines are going to have to use two sets of HTML code, and I think it's just one of those things that will fall through the cracks, one way or another, for a long time yet.. though I hope not :)

-Suzy

[edited by: SuzyUK at 1:38 am (utc) on Jan. 23, 2008]

[zarforpar]

That makes total sense, and I completely recognize how frustrating the "standards" can be when some players (big, lumbering, industry megaliths) don't think that those "standards" are their standards. I've been reading about capability detection as a better option to browser sniffing, and wondering whether this would be the sort of thing that one could do such detection for, and how. Obviously, this is an edge case at the moment, but it's gotten me thinking and wishing.

So, is it possible to detect for css3 support, or for support for this property (for example), and how would it be done?

Thanks again,

[swa66]

CSS1 became a recommendation on 17 Dec 1996, was revised 11 Jan 1999.
CSS2 became a recommendation on 12 May 1998.
CSS2.1 is a candidate for recommendation since 19 July 2007

As you can see the entire thing got a serious slowdown.
But don't hold your breath, even IE7 doesn't support everything in the CSS1 standard, even if it predates IE7 by more than a decade.

IMHO: unless the browsers (mostly IE) clean up their act considerably, CSS3 is only dreaming of what could be done.