- From: docfaraday via GitHub <noreply@w3.org>
- Date: Fri, 27 Feb 2026 00:25:49 +0000
- To: public-webrtc-logs@w3.org
> I think today's design principle is more about keeping implementation-defined behavior out of specs, because it's inherently web incompatible. Ok, that's fine with me. I'm not interested in doing that. What I am asking is to give enough room to allow the implementation to do the right thing wrt transport protocol; to not *force* the implementation to do something broken, like leaving a transport hanging. > A UA that doesn't GC its connection until either the web app explicitly closes it or the web app is unloaded, is a valid implementation. I mean, I guess. If an implementation decides not to clean up after itself, it is that implementation's prerogative. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3090#issuecomment-3970022814 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 February 2026 00:25:50 UTC