Comparing d80d31897c..6265953858 - meet

gsadmin/meet

Fork 0

mirror of https://github.com/suitenumerique/meet.git synced 2026-09-02 13:48:26 +00:00

Author	SHA1	Message	Date
lebaudantoine	6265953858	🔒️(frontend) fix HIGH CVEs in libexpat 2.8.2-r0 Address the following HIGH severity CVEs in libexpat 2.8.2-r0, reported by Trivy: * CVE-2026-66046 * CVE-2026-76641	2026-09-02 14:56:09 +02:00
kaelvar	0edac91793	✨(frontend) add 1080p sending resolution option The sending resolution selector stopped at 720p while `VideoPresets` already exposes `h1080` (1920x1080), so publishers on a good uplink could not make use of the capacity they had. Add "Very high definition (1080p)" above the existing entries, translated in the five supported locales. The default stays `h720`, so nothing changes unless a user goes and picks the new entry. Being explicit about what that costs, since 1080p roughly doubles a publisher's uplink: this is a per-user choice, and an instance operator has no way today to decline it. Whether that warrants a server-side setting alongside the existing `ApiConfig` flags is a call for maintainers — happy to add one if you want it, rather than change the API contract unasked in a frontend PR. While here, make the option list harder to get wrong. Resolutions now come from a single `VIDEO_RESOLUTIONS` tuple that `VideoResolution` derives from, the selector items are built by mapping over it against a `Record<VideoResolution, string>` of labels — so a resolution cannot be added to one and forgotten in the other — and a persisted value that is not in the tuple falls back to `h720` instead of reaching `VideoPresets[...]` as `undefined`, since `loadUserChoices` spreads localStorage without validating it. Known limitation, unchanged by this patch: `restartTrack` passes the resolution as an `ideal` constraint, so a camera that cannot reach the selected height degrades silently. That is already true of 720p on a 480p webcam; 1080p is the first step where the gap is the common case rather than the edge one.	2026-09-02 14:35:00 +02:00

Author

SHA1

Message

Date

lebaudantoine

6265953858

🔒️(frontend) fix HIGH CVEs in libexpat 2.8.2-r0

Address the following HIGH severity CVEs in libexpat 2.8.2-r0,
reported by Trivy:

* CVE-2026-66046
* CVE-2026-76641

2026-09-02 14:56:09 +02:00

kaelvar

0edac91793

✨(frontend) add 1080p sending resolution option

The sending resolution selector stopped at 720p while `VideoPresets` already
exposes `h1080` (1920x1080), so publishers on a good uplink could not make use
of the capacity they had. Add "Very high definition (1080p)" above the existing
entries, translated in the five supported locales.

The default stays `h720`, so nothing changes unless a user goes and picks the
new entry. Being explicit about what that costs, since 1080p roughly doubles a
publisher's uplink: this is a per-user choice, and an instance operator has no
way today to decline it. Whether that warrants a server-side setting alongside
the existing `ApiConfig` flags is a call for maintainers — happy to add one if
you want it, rather than change the API contract unasked in a frontend PR.

While here, make the option list harder to get wrong. Resolutions now come from
a single `VIDEO_RESOLUTIONS` tuple that `VideoResolution` derives from, the
selector items are built by mapping over it against a
`Record<VideoResolution, string>` of labels — so a resolution cannot be added
to one and forgotten in the other — and a persisted value that is not in the
tuple falls back to `h720` instead of reaching `VideoPresets[...]` as
`undefined`, since `loadUserChoices` spreads localStorage without validating
it.

Known limitation, unchanged by this patch: `restartTrack` passes the resolution
as an `ideal` constraint, so a camera that cannot reach the selected height
degrades silently. That is already true of 720p on a 480p webcam; 1080p is the
first step where the gap is the common case rather than the edge one.

2026-09-02 14:35:00 +02:00

Compare commits

2 Commits

main .. feat/1080p-publish-resolution

Diff Content Not Available

Compare commits

2 Commits main .. feat/1080p-publish-resolution

Diff Content Not Available

2 Commits

main .. feat/1080p-publish-resolution