- From: Ryan Sleevi <sleevi@google.com>
- Date: Sat, 1 Mar 2014 14:57:55 -0800
- To: Richard Barnes <rlb@ipv.sx>
- Cc: public-webcrypto@w3.org, Alexey Proskuryakov <ap@webkit.org>
Received on Saturday, 1 March 2014 22:58:22 UTC
My +1 on this point is long known :) Do we even have aliases defined at this point? For the longest time the spec was silent on how to map them (since the proposal was in the context of JWE/JWS) On Mar 1, 2014 2:54 PM, "Richard Barnes" <rlb@ipv.sx> wrote: > 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:58:22 UTC