[whatwg] Inconsistent behavior for empty-string URLs

Mike Taylor michaelaarontaylor at gmail.com
Tue Dec 15 17:51:19 PST 2009


Shouldn't this proposal take into account the CSS3 content property? (
http://www.w3.org/TR/css3-content/)

 E.g., figure[alt] { content: attr(href, url), attr(alt); }


This was discussed not too long ago, starting in this thread:
Adding a src attribute to all elements (
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-November/023955.html
)

-Mike

On Tue, Dec 15, 2009 at 8:37 PM, Nicholas Zakas <nzakas at yahoo-inc.com>wrote:

> Yes, that sounds right.
>
> -Nicholas
>
> ______________________________________________
> Commander Lock: "Damnit Morpheus, not everyone believes what you
> believe!"
> Morpheus: "My beliefs do not require them to."
>
> -----Original Message-----
> From: Jonas Sicking [mailto:jonas at sicking.cc]
> Sent: Tuesday, December 15, 2009 5:22 PM
> To: Nicholas Zakas
> Cc: Maciej Stachowiak; whatwg at lists.whatwg.org; Aryeh Gregor; Simon
> Pieters
> Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs
>
> On Tue, Dec 15, 2009 at 4:11 PM, Nicholas Zakas <nzakas at yahoo-inc.com>
> wrote:
> > Here's what I would propose:
> >
> > 1. Empty string attributes for HTML elements specifying resources to
> > automatically download are considered invalid and don't cause a
> request
> > to be sent. Examples: <img>, <link>, <script>, <iframe>, etc. This
> would
> > not apply to <a href=""> because it is a user-initiated request.
> >
> > 2. This also applies to manipulation of HTML elements through the DOM,
> > so (new Image()).src="" would not result in a request being sent.
> >
> > 3. This does not apply to JavaScript APIs that are unrelated to HTML
> > elements, such as Web Workers, XMLHttpRequest, etc.
>
> I'd prefer to explicitly enumerate the elements we're talking about,
> rather than giving rules which risk being interpreted differently by
> different people.
> For example not all <link>s are automatically downloaded, such as
> <link rel=prev>. However I suspect that we'll want all <link>s to
> behave the same.
>
> So the specific list would then be:
>
> <img>
> <link>
> <script>
> <iframe>
> <video>
> <audio>
> <object>
> <embed>
> <source>
> <input type=image>
>
>
> All of these would never attempt to fetch a resource if the src/href
> attribute is empty (even if the current baseuri is different from the
> document uri). However it would not act as if the attribute was not
> set (important for <script>).
>
> Does that sound right?
>
> / Jonas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091215/39e61d6c/attachment-0002.htm>


More information about the whatwg mailing list