- From: Harald Alvestrand via GitHub <noreply@w3.org>
- Date: Fri, 17 Apr 2026 07:38:24 +0000
- To: public-webrtc-logs@w3.org
> > wrt the h.264 profile-level tests, I support leaving these out of Interop2026. > > [@alvestrand](https://github.com/alvestrand), agreed with leaving it out. But I think it would still be good to determine what should be done here. A few options: > > 1. UA enforces that video with too many pixels for the profile is not sent. > 2. UA upgrades to a profile that allows video with many pixels to be sent. > 3. UA downgrades the video to a level that allows to use the profile. > > If going for 3, spec should probably document how to downgrade (resolution, framerate, both...). @youennf this is probably deserving of its own issue. My immediate thought is that a profile restriction should be treated just like a bandwidth or cpu restriction (except that we can never increase it), and that downgrading should be directed by degradation-preference settings. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3100#issuecomment-4266236938 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 April 2026 07:38:25 UTC