W3C home > Mailing lists > Public > public-webcrypto@w3.org > March 2014

Re: Bug 24878 - Remove algorithm aliases

From: Richard Barnes <rlb@ipv.sx>
Date: Sat, 1 Mar 2014 22:53:51 +0000
Message-ID: <CAL02cgSM5G86JwcC5ixM258fgRgYC=nLki-Deng+8XBj8C133Q@mail.gmail.com>
To: Alexey Proskuryakov <ap@webkit.org>
Cc: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
But is there really any use case besides "it's silly and saves the
developer a few characters"?  It seems like apps are going to define
aliases anyway, so there's not much point to the browser doing it as well.


On Sat, Mar 1, 2014 at 6:55 PM, Alexey Proskuryakov <ap@webkit.org> wrote:

> Hi Richard,
>
> 01 марта 2014 г., в 8:39, Richard Barnes <rlb@ipv.sx> написал(а):
>
> FYI, I just filed Bug 24878, proposing that we remove algorithm aliases.
>  The current Chromium implementation doesn't do them, and I'm hoping to
> save a few lines in Firefox :)
>
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=24878
>
>
> Are you talking about DOMString aliases as used in this example?
>
> crypto.subtle.digest('sha-1', myArray)
>
> WebKit supports this, and it seems silly to require passing "{name:
> 'sha-1'}" here.
>
> - WBR, Alexey Proskuryakov
>
>
Received on Saturday, 1 March 2014 22:54:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:02:40 UTC