feat(cdp): report the native video sender capabilities #118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "agent/atlas-native-codec-20260912"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Isolation qualification currently queries renderer-side RTCRtpSender capabilities even though the native browser-process PeerConnectionFactory owns streaming. This can reject the custom encoder because the unrelated renderer advertises VP8.
Add browser-scope Cb.getVideoSenderCapabilities, lazily querying the installed native PCF. It returns its source discriminator and every codec name unchanged; missing wiring or an unavailable/empty factory returns a CDP error. Add the protocol contract and a repeated read-only probe in the existing CDP validation suite. Consumers must retain no-VP8 plus approved-codec enforcement and bind observations to the authenticated allocation and image provenance.
Validation: baseline make verify passed; changed-tree make lint, Python syntax validation and git diff --check passed. The exact-source chromeless-build-atlas-native-codec-20260912 job completed successfully: all 11 selected targets compiled/linked, seven unit-test binaries ran successfully, and the binary was packaged. The audio test was explicitly skipped. The new CDP probe has NOT run against a built guest (the compile lane skips CDP validation). Producer build/live qualification and consumer changes remain required; the current isolation gate and image pins are unchanged.