I agree 100%. IMO, best would be, as you say, to pass the hash in a separate attribute. Second best would be to put it in the query (http://mirror.com/file?sha256=abc123). But, changing the meaning of the fragment? That's just silly!
Let's say I want to send someone to a specific section, sec2, in a page on a remote site. Let's say further that I need to verify that the page is *exactly* what I was expecting.
<a href="http://mirror.com/a.html#sec2" hash="sha256:abc123"> -- attribute works
<a href="http://mirror.com/a.html?hash=sha256:abc123#sec2"> -- query works
<a href="http://mirror.com/a.html#sec2hash=sha256:abc123"> -- fragment fails!
Let's hope they give this some more thought...
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds