[QA] §D Element Call control-bar regression sweep (PTT, AFK auto-mute, denoise, screenshare audio, PiP badges) #173
Closed
opened 2026-09-17 23:24:06 -04:00 by jared
·
2 comments
No Branch/Tag Specified
lotus
update-packages
sw-fix
read-me-update
image-path-changes
dm-calls
fix-2469
renovate/element-hq-element-call-embedded-0.x
renovate/npm-i18next-http-backend-vulnerability
renovate/npm-vite-vulnerability
dev
docs-update
more-theme
fix-257
imporve-thread-reply
revert-2402-improve-menu-congestion
mxidColor-toggle
update-sw-main-msg
v4.11.1
v4.10.5
v4.10.4
v4.10.3
v4.10.2
v4.10.1
v4.10.0
v4.9.1
v4.9.0
v4.8.1
v4.8.0
v4.7.1
v4.7.0
v4.6.0
v4.5.1
v4.5.0
v4.4.0
v4.3.2
v4.3.0
v4.2.3
v4.2.2
v4.2.1
v4.2.0
v4.1.0
v4.0.3
v4.0.0
v3.2.0
v3.1.0
v3.0.0
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.8.2
v1.8.1
v1.8.0
v1.7.0
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.0
v1.3.2
v1.3.1
v1.3.0
v1.2.1
v1.2.0
v1.1.0
v1.0.0
Labels
Clear labels
a11y
area: appearance
area: auth-session
area: build-ci
area: calls
area: desktop
area: media
area: messaging
area: mobile
area: moderation
area: navigation
area: notifications
area: settings
area: threads
bug
dependencies
docs
duplicate
enhancement
help wanted
invalid
needs-human-review
performance
planning
priority: critical
priority: high
priority: low
priority: medium
qa
question
research
security
tech-debt
ux
wontfix
Accessibility: keyboard, screen reader, contrast, motion
Client area: appearance
Client area: auth-session
Client area: build-ci
Client area: calls
Client area: desktop
Client area: media
Client area: messaging
Client area: mobile
Client area: moderation
Client area: navigation
Client area: notifications
Client area: settings
Client area: threads
Something is not working
Third-party package versions and advisories
README / LOTUS_* docs wrong or missing
This issue or pull request already exists
New feature
Need some help
Something is wrong
Re-render storms, leaks, heavy work on hot paths
Data loss, security hole, or crash on a main path
Broken feature or serious usability problem
Minor issue or polish
Wrong behaviour in an edge case or notable degradation
Manual QA: shipped, needs a human in a real environment
More information is needed
XSS, unsafe URLs, data leaks, auth/session
Code health, dead code, fragile patterns
Usability or visual inconsistency
This won't be fixed
Milestone
No items
No Milestone
Manual QA backlog
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: LotusGuild/cinny#173
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Migrated from
LOTUS_TESTING.md§D on 2026-09-17 — the file is now reference-only.How to report: tick each item as it passes; on FAIL comment with what you saw vs expected, browser/OS, web (chat.lotusguild.org) vs desktop (Tauri), theme, and any browser-console errors. Screenshots for anything visual.
The upstream bump changed EC's internals and DOM selectors; our call controls drive that iframe, so sweep them. In a live call with 2 people, confirm each of our control-bar buttons works:
If any control does nothing, that usually means an EC DOM selector changed — capture the console and tell me which button.
Verified in real two-party calls on a local stack (Synapse + LiveKit 1.13.7 + voice-limit-guard + the bundled EC fork; two headless Chromiums with fake mic/camera, a 440 Hz tone as the mic)
data-muted,io.lotus.call_state.audioEnabledfollows9fefd149), it now restores the mic it took away (Discord semantics)document.fullscreenElementset, label → Exit Fullscreen)audioEnabled:trueon the fork; release → falseio.lotus.call_state(50 messages in 12 s,speaking:truewhile the tone plays)230d147e) — see #2950b4e2c1) — see #161Reload mid-call: no auto-rejoin (#118 still open); the leftover membership is cleaned by the MSC4140 delayed leave within ~30 s, so no long-lived ghost.
The stack is
scripts/dev-homeserver.sh callsnow, so this sweep is repeatable. Leaving open only for the unexercised rows.Swept end-to-end on the local calls stack (Synapse + LiveKit + JWT service + voice-limit-guard, two headless Chromium clients with fake mic/camera/desktop-capture; ground truth taken from the SFU's
ListParticipants, the fork'sio.lotus.call_statestream and theRemoteTrackPublicationbehind each<audio>element — not just from our button labels). Web/Chromium only; desktop (Tauri) is tracked in cinny-desktop.AUDIO/MICROPHONE(muted)/ unmutedVIDEO/CAMERAappears/disappears on the SFU; other side'scall_state.videoEnabledfollows<audio>muted=true, server-sidesetEnabled(false); undeafen restores; key + new on/off switch verified in the Push-to-Deafen fixVIDEO/SCREEN_SHARE+AUDIO/SCREEN_SHARE_AUDIOpublished; stop removes themsetVolume(0)we used. Fixed in the fork (0.25.0-lotus.4, mute now rides the renderer'smutedprop like deafen) and pinned in68ce13f0. Verified: re-published track mountsenabled=falsewhile muted, re-enables on unmute; deafen+undeafen keeps it muted; leaving the call resets itinput[value=spotlight]becomes checked and the item flips to "Grid View"; Reactions opens the picker ("Pick reaction 👍 🎉 …"); Settings opens EC's Audio/Video/Preferences dialogm.call.memberstate immediately(muted)lotusDenoiseSource=true,df_bg.wasm+ model fetched, other side hears the mic (RMS 0.12–0.25 with a pure-tone input) and getsspeaking=true; survives an SFU restart (audio back within ~2 s). By-ear quality is a human item → new issueExtras found along the way:
SecurityErrorreading the now-cross-origin frame — fixed in70620d4b(getCallDocument()).Closing; the by-ear rows live in the new human-QA issue.