Re: <meta http-equiv="Link"> question

Anne van Kesteren, Wed, 04 Aug 2010 19:37:20 +0200:
> On Wed, 04 Aug 2010 19:31:15 +0200, Jonas Sicking <> wrote:
>> On Tue, Aug 3, 2010 at 11:26 PM, Anne van Kesteren 
>> <> wrote:
>> For what it's worth, I'd be happy to remove support for this assuming
>> it doesn't "break the web".

Did you, before saying this, consider that Mozilla also supports link 
prefetching via http-equiv="link"? [1] 

>> shows no results, but I'm not sure how much content that searches.

My fist search result for http-equiv="link", was quite interesting ... 

> I doubt it breaks the Web given that only Opera and Mozilla support 
> it. I'm fine with dropping it from Opera too.

Could we also remove http-equiv="default-style" [3], with the same 
justification? (No support, except in Opera and Mozilla.)

Btw, I slightly disagree with the bug report: [5] Opera an Mozilla's 
treatment of http-equiv="Link" is quite in line with HTML4's general 
specification of META: [4]

]] Note. When a property specified by a META element takes a value that
   is a URI, some authors prefer to specify the meta data via the LINK

>>> Browsers also support Set-Cookie here:
>> I feel less strongly about Set-Cookie. There is no fully equivalent
>> feature, so we'd have to check if people find this feature useful or
>> not.
> Per that bug sites are actually using this unfortunately. There is an 
> equivalent feature of course, the Set-Cookie header at the HTTP level 
> :-) And the document.cookie API.

FWIW, also mention http-equiv="Set-Cookie". [2]

leif halvard silli

Received on Wednesday, 4 August 2010 19:24:02 UTC