W3C home > Mailing lists > Public > www-style@w3.org > June 2016

Re: [css-values] Readibility Poll

From: Zack Weinberg <zackw@panix.com>
Date: Thu, 9 Jun 2016 09:04:29 -0400
Message-ID: <CAKCAbMi-BydjjKsUugA5bYxtp+LwWowCdmu9o6j9hqwZkfo=OQ@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "www-style@w3.org" <www-style@w3.org>
On Wed, Jun 8, 2016 at 7:56 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
> Wrt resolution in
> https://lists.w3.org/Archives/Public/www-style/2016May/0209.html
> Preferences on wording?
>
> Version A:
>
>   If a ''url()''’s value starts with a U+0023 NUMBER SIGN (<code>#</code>),
>   parse and compute it as described above for relative URLs,
>   but always resolve that fragment against the currently-active base URL.
>   This reference must always be treated as same-document
>   (rather than cross-document).
>   Additionally, when serializing such a ''url()'',
>   serialize just the fragment.
>
> Version B:
>
>   If a ''url()''’s value starts with a U+0023 NUMBER SIGN (<code>#</code>),
>   parse it as per normal for URLs,
>   but additionally set the “local url flag” of the ''url()''.
>
>   When matching a ''url()'' with the <a>local url flag</a> set,
>   ignore everything but the URL's fragment,
>   and resolve that fragment against the current document
>   that relative URLs are resolved against.
>   This reference must always be treated as same-document
>   (rather than cross-document).
>
>   When serializing a ''url()'' with the <a>local url flag</a> set,
>   it must serialize as just the fragment.

I find A clearer and easier to follow.

zw
Received on Thursday, 9 June 2016 13:04:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:47 UTC