- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Fri, 27 Feb 2004 00:25:29 -0500
- To: www-style@w3.org
> 2. the keyword name of 'tab' seems too implementation-specific.
It's also incredibly intrusive, in my opinion, unless we plan to restrict use
of this property to user/ua stylesheets. I can see pages being able to request
a new "rendering surface", but it should be up to the UA how this is presented
to the user. If the user wants each "rendering surface" in its own window, for
example, that's what the UA should do, no matter whether it supports tabs,
thumbnails, true MDI, or whatever. That preference doesn't have to be set via
CSS to work fine. CSS may give more options, but I can hardly imagine users
actually writing user sheets that will open some links in tabs and others in
windows and still others in thumbnails.
I realize that some authors want this (as the repeated bugs filed on Mozilla to
that effect attest), but I think this should be a case of having some spine and
NOT letting them have it... because otherwise any UA that really wants to cater to its
users will end up having a preference that does the equivalent of setting this
to some value in the user sheet with a !important set. Same effect, lots of
wasted effort.
I also agree with J. King's comments about the 'none' value for this property.
So I feel that this whole property should just be dropped, I guess... ;)
Boris
--
Modern art is what happens when painters stop looking at girls and
persuade themselves that they have a better idea.
-- John Ciardi
Received on Friday, 27 February 2004 00:25:30 UTC