See <https://www.w3.org/Bugs/Public/show_bug.cgi?id=19416>, it doesn't make sense for keyUsage to have the default empty value.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19705 is the correct bug.
Created attachment 240848 [details] Patch
Comment on attachment 240848 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=240848&action=review This patch does not change behavior - everything besides the function name is essentially a comment for [Custom] properties. The actual implementation that makes these optional is in JSSubtleCryptoCustom.cpp. It is probably OK to make this particular change. But I think that the better approach would be to freeze the existing implementation under crypto.webkitSubtle, and start one that matches the new spec and is exposed as crypto.subtle. There were incompatible changes that we shouldn't be making for webkitSubtle. And generally, the spec changed so much that a clean reimplementation is probably easier than massaging the existing one. > Source/WebCore/ChangeLog:8 > + No new tests, no behavior change. There is indeed no behavior change (see above), however making arguments non-optional is definitely a behavior change that needs to be tested.
<rdar://problem/27858197>
This bug should be resolved by the following revisions: <http://trac.webkit.org/changeset/207809>, <http://trac.webkit.org/changeset/208548>, <http://trac.webkit.org/changeset/208737>, <http://trac.webkit.org/changeset/208891>, <http://trac.webkit.org/changeset/208918>, <http://trac.webkit.org/changeset/209092>, <http://trac.webkit.org/changeset/209150>, <http://trac.webkit.org/changeset/209164>, <http://trac.webkit.org/changeset/209166>, <http://trac.webkit.org/changeset/209191>, <http://trac.webkit.org/changeset/209155>, <http://trac.webkit.org/changeset/209200>.