[whatwg] Issues concerning the <base> element and xml:base

[Calogero Alex Baldacchino]

Ian Hickson ha scritto:
> On Fri, 16 Jan 2009, Calogero Alex Baldacchino wrote:
>   
>> What should happen to a linked style sheet disabled during the first 
>> casced and enabled after the <base> has been changed? Or if it was first 
>> enabled, than disabled before changing the <base>, and re-enabled after?
>>     
>
> For external resource links created with the <link> element, the URL is 
> resolved when the resource is fetched, which can be delayed if the 
> resource doesn't apply yet (e.g. because a media query doesn't yet match). 
> This could lead to situations where different user agents had compliant 
> behavior, unfortunately, but this is one case where I can't see how to 
> avoid it without requiring suboptimal behavior.
>
>   

I understand. Perhaps, if a main (more diffused) behaviour could be 
isolated, it might be chosen to "normalize" newer UAs behaviours, while 
possibly breaking fewer existing pages (the same eventually behaving 
differently in different browsers). However, I guess this might require 
a convergence between HTML and CSS specifications for this purpose (it 
might rise an issue on consistence for @import rules, for instance, 
which are in CSS scope).

I don't know if it may work something like establishing that a URL, in 
this case, is resolved any times it is explicitly set (e.g. when the 
document is parsed and when the "href" value changes), as if the 
resources were immediately fetched (thus, not being affected by a 
successive change in a <base>) but not constraining UAs to do so (an 
inline style element might be treated as an external resource being yet 
fetched, thus it would be about to associate it with a base URI being 
valid at the moment the style was created and maintained valid until the 
style content is explicitely changed). Though, I guess this should be 
somehow consistent with existing UAs and pages (or, at least, with a 
significant group).


Anne van Kesteren ha scritto:
> On Fri, 16 Jan 2009 05:15:41 +0100, Ian Hickson <ian at hixie.ch> wrote:
>> For external resource links created with the <link> element, the URL is
>> resolved when the resource is fetched, which can be delayed if the
>> resource doesn't apply yet (e.g. because a media query doesn't yet 
>> match).
>> This could lead to situations where different user agents had compliant
>> behavior, unfortunately, but this is one case where I can't see how to
>> avoid it without requiring suboptimal behavior.
>
> You have the same scenario for inline <style> elements that are either 
> in alternate state or are of a medium that currently does not apply to 
> the document. The user agent is not required to parse those CSS blocks 
> directly, I believe.
>

WBR, Alex
 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Innammorarsi è facile con Meetic, milioni di single si sono iscritti, si sono conosciuti e hanno riscoperto l'amore. Tutto con Meetic, prova anche tu!
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8292&d=17-1