[whatwg] <INCLUDE> and links with @rel=embed
svartman95 at gmail.com
Fri Apr 29 08:22:26 PDT 2011
On 4/28/11, Ian Hickson <ian at hixie.ch> wrote:
> On Thu, 28 Apr 2011, Bjartur Thorlacius wrote:
>> All current UAs would understand the link (and most probably present it
>> to the user). Inline presentation is an optional luxury: the important
>> thing is getting the media across. I, for one, can't find any sign of
>> <source> support in wget, and a few other "non-mainstream" UAs.
> Well for <video> fallback people are likely to use <a> as well, but I
> don't think it makes sense to force every <source> to be a link.
Writing both <source> and <a> for every source seems like unnecessary
duplication to me. The primary difference between the two is that the
resource referenced by the former is to be displayed inline, but the
resource referenced by the latter is to be accessible interactively.
<a style="content: url(attr(href));" href="/usr/videos/lolcatz">Funny
cats jumping around</a>.
Ok, this isn't valid CSS, but you get my thinking (I hope).
More information about the whatwg