W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2006

[whatwg] hash Attribute

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 10 Nov 2006 01:04:49 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0611100103180.4414@dhalsim.dreamhost.com>
On Thu, 9 Nov 2006, Gervase Markham wrote:

> Ian Hickson wrote:
> > If the idea is that UAs that implement this would stop you from using the
> > file if the checksum didn't match, then this would just cause users to use
> > browsers _without_ this feature to download files, since those browsers
> > wouldn't complain about data corruption. "It works when I use IE to download
> > the file but when I use Camari, it says 'checksum error'."
> 
> Hopefully, it would instead say:
> 
> "The file you have downloaded has been corrupted or tampered with."

"It works when I use IE but when I use Camari, it says that the file has
been corrupted." "Oh man, I'm not using Camari then! I don't need my music 
to get corrupted!"

 
> [Delete File] [Keep Unsafe File]

"Keep Unsafe File" would make the feature as useless as SSL certificates 
are today.


> It might even just delete it without asking you. After all, you haven't 
> actually got the file you wanted - or that the person linking wanted you 
> to have. If they didn't want this behaviour, they wouldn't have used a 
> URL with a hash.

Exactly. But then you're back to the "it works in the older browser" 
problem.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 9 November 2006 17:04:49 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:49 UTC