Re: [fetch] error types too vague for TLS certificate error (#205)

FWIW (browser security guy here) while I would have very serious reservations about exposing granular error information to JS (because there's private information there that we don't want to expose without user consent), I would be totally fine putting information like this in the dev console.   I think both Chrome and Firefox already do so, just not in the area your screenshot shows.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/205#issuecomment-196597369