Re: Bug 24878 - Remove algorithm aliases

Obviously, we've long since abandoned any semblance of JWE/JWS
compatibility.

AFAICT, there are none defined in the spec.  And in order to be useful,
they'll need to be in the spec; browser-specific ones would be more of an
inconvenience than a shortcut.


On Sat, Mar 1, 2014 at 10:57 PM, Ryan Sleevi <sleevi@google.com> wrote:

> 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
>>>
>>>
>>