- From: Ernest Cline <ernestcline@mindspring.com>
- Date: Mon, 8 Dec 2003 22:18:55 -0500
- To: "Afternoon" <afternoon@uk2.net>, www-style@w3.org
> [Original Message]
> From: Afternoon <afternoon@uk2.net>
>
> ... What about subdomains? Would the user have to exclusively list them:
>
> @scope url("http://www.yahoo.com/"), url("http://dir.yahoo.com/"),
> url("http://uk.yahoo.com/"), url("http://finance.yahoo.com/"),
> url("http://groups.yahoo.com/"), url("http://login.yahoo.com/"),
> url("http://shopping.yahoo.com/"), url("http://privacy.yahoo.com/") {
> body {
> background-color:blue;
> }
> }
>
> But all this is moot if people who have a hard time reading my peach
> text on a purple background or who can't find your text-decoration:none
> links can't actually override our settings specifically with their UA.
There are sites out there with domain setups like:
example.com
foo.example.com
bar.example.com, etc.
so I wouldn't want an @scope rule like:
@scope url("http://example.com") {}
to necessarily work on the other two domains.
I'll grant that being able to do so would be nice in most cases,
but any such syntax should require it to be explicitly stated somehow.
perhaps it would be possible to borrow the prefixes from
the attribute selectors to enable that sort of specificity somehow.
If only domains were left to right just as the rest of a URL was,
it would be very easy.
Received on Monday, 8 December 2003 22:20:58 UTC