-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File a WebIDL issue to add the DOMException names WebRTC needs #495
Comments
I think these have been addressed in tip-of-tree and should be visible with the next editor's draft publication to github.io. |
Adam will close this one when the new editors' draft with the fixes is pushed. |
So, in the end will no new DOMException names at all be needed? And where can I read the tip-of-tree version online? |
@foolip https://w3c.github.io/webrtc-pc/ but it's not updated frequently enough. What I do: Click "Code" tab above, then on "Latest commit xxx n days ago", then on E.g. https://rawgit.com/w3c/webrtc-pc/1949648d8cfc109bbc41a787a868adf16ce7af59/webrtc.html |
Thanks @jan-ivar, it looks like the spec now uses |
|
@martinthomson, would like your thoughts on jan-ivar's question. I had the same question. |
I think that it probably isn't an error. Maybe try to address that in a different issue though. |
so it sounds like this issue can be closed, and maybe @jan-ivar could raise a new one on whether IdPLoginError needs to be a real error. |
I'm OK with closing this if a new issue to sort out https://w3c.github.io/webrtc-pc/#sec.idp-loginneeded is filed. Two things seem in need of some attention:
|
@foolip that sounds like the right information. Want to file the issue? |
I'd be delighted: #555 |
The exception name is TBD in most places, but one place uses IdpError.
Please file an issue or pull request similar to whatwg/webidl#85 with the DOMException names this spec will used.
This came up in https://codereview.chromium.org/1661493002/
The text was updated successfully, but these errors were encountered: