Fix our webcrypto web platform test failures

NEW
Unassigned

Status

()

Core
DOM: Security
P3
normal
4 months ago
3 months ago

People

(Reporter: bz, Unassigned)

Tracking

53 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [domsecurity-backlog1])

http://searchfox.org/mozilla-central/search?q=&path=testing%2Fweb-platform%2Fmeta%2Fwebcryptoapi shows a ton of failures in various web platform tests for webcrypto.

This is popping up in marketing materials from Apple and whatnot; see things like https://twitter.com/webkit/status/888466862002106368

Some of these are fairly simple (e.g. incorrect type of exception thrown), but some are us actually not following the specs correctly (e.g. the very first one I tried at http://w3c-test.org/WebCryptoAPI/generateKey/test_failures_ECDH.https.html shows us not failing operations that should fail).
Flags: needinfo?(ttaubert)
I would love to fix those but I definitely won't find the time to do so in the next months :( They should be relatively easy fixes, but then OTOH getting WebCrypto work prioritized is hard. I tried.
Flags: needinfo?(ttaubert)
JC: this is hurting us currently. I've tagged this as "backlog" for now based on Tim's comment, but you ought to determine where it's scheduled in fact.
Flags: needinfo?(jjones)
Whiteboard: [domsecurity-backlog]
This isn't just about error codes, these would be somewhat easy fixes, we're missing features too. We deemed WebCrypto not important enough to spend time on for years, why does one WebKit blog post change that suddenly?

Comment 4

4 months ago
I've added this to the SecEng roadmap and my team's backlog, Dan.
Flags: needinfo?(jjones)
Priority: -- → P3
Whiteboard: [domsecurity-backlog] → [domsecurity-backlog1]
You need to log in before you can comment on or make changes to this bug.