ISSUE-3: Should we refactor the generic guidance on error handling out of the spec
Should we refactor the generic guidance on error handling out of the spec
- State:
- RAISED
- Product:
- Raised by:
- Eric Rescorla
- Opened on:
- 2013-11-12
- Description:
- The spec is full of "If connection's RTCPeerConnection signalingState is closed, throw an InvalidStateError exception and abort these steps."
I propose to pull this out and make it apply everywhere to the spec and then list the explicit exceptions. - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from ekr@rtfm.com on 2013-11-14)
- Re: ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from martin.thomson@gmail.com on 2013-11-14)
- Re: ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from harald@alvestrand.no on 2013-11-14)
- ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from sysbot+tracker@w3.org on 2013-11-12)
Related notes:
No additional notes.
Display change log