Re: [css-values] url(#frag) handling when base url changes

On 03/22/2016 02:55 PM, Simon Pieters wrote:
> On Tue, 22 Mar 2016 18:52:35 +0100, Tab Atkins Jr. <> wrote:
>> On Mon, Mar 21, 2016 at 6:23 PM, fantasai <> wrote:
>>> I'm.. not 100% clear on what's going on here, but, isn't this handled
>>> by the fact that CSS is stateless? It's only a problem if the computed
>>> value is cached over the base URL change--and that's a caching problem,
>>> not a spec problem.
>> CSS is not, in fact, stateless for this issue.  Style-Attr requires
>> the URL to be absolutized at parse-time.  Values says URLs are
>> absolutized at computed-value time.  The web platform in general is
>> not consistent on whether things are "stateless" or not for base-URL
>> changes; <img>, for example, does not reload (tho it does change its
>> serialization of the src attribute), and this behavior is
>> well-specified by HTML.
>> I put together a test-case at
>> <>.
> Nice! I had started a simpler test at
> I think nothing anywhere says to do anything in particular for CSS when
> the base URL changes, which probably means that the URLs in CSS shouldn't
> be reparsed, right?

There's a comment in the spec source saying that hixie intended for dynamic
changes to the base URL to not affect style.

I'm not sure the rationale why...


Received on Wednesday, 23 March 2016 16:06:22 UTC