- From: Ian Denhardt via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Jun 2021 19:18:32 +0000
- To: public-webrtc-logs@w3.org
Outstanding issues as I see them: - @alvestrand says he's not sold on the idea. Could you elaborate on your objection? - @annevk raised concerns regarding new places exceptions may be raised. Relevant things to decide there: - Are we ok with a new exception being thrown if an operator sets this? - Do we think pushing the error reporting later is worth the extra complexity, and if so where would this go instead? - If we keep the current design, how might this evolve if we make the csp directive finer-grained? I'm of the opinion that the additional complexity is *not* worth it for the error handling consideration alone, but am interested in hearing other perspectives. I don't have a great answer to the evolvability question though. I also am not sure where the check should go if we push it later -- if others have insights please share. My biggest concern with pushing the check later is I want to have a clear story as to how we will have confidence that we haven't missed a spot. -- GitHub Notification of comment by zenhack Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/81#issuecomment-858025815 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 June 2021 19:19:15 UTC