From: Juliusz Chroboczek <jch@irif.fr>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: galene@lists.galene.org
Subject: [Galene] Re: ANNOUNCE: Galene 1.2
Date: Sun, 06 Sep 2026 11:32:39 +0200 [thread overview]
Message-ID: <87ecf6d8so.wl-jch@irif.fr> (raw)
In-Reply-To: <87o6ebtp9v.fsf@toke.dk>
Hi Toke, I hope you had a nice vacation.
> Very nice!
Thanks. I think it's overdue, users have been complaining about not being
able to check before joining. I'm rather pleased with the use of
a disclosure triangle, I think it works better than my initial prototype
that used a popup window.
> However, the camera test only shows "Camera 1" and "Microphone 1" on
> Firefox; in Chromium it seems to work well enough.
Yeah. This is due to
https://bugzilla.mozilla.org/show_bug.cgi?id=1935371
The API that we use to get the list of devices is called enumerateDevices.
Of course, it's a great source of fingerprinting material, so it is
restricted in various ways by different browsers. Chromium-based browsers
do not expose device labels before the user has granted the camera
permissions. Firefox is more radical, it refrains from listing cameras and
microphones unless there is a camera stream already running. Or something
like that, the exact behaviour is not documented.
> I can select a different camera/microphone on Firefox after joining and
> turning on the camera; but until I turn on the camera there's only the
> same "Microphone 1"/"Camera 1" available in the menu. Perhaps that's
> related?
In Galene proper, I work around the issue by populating the camera menu
a second time after the user has opened a camera stream (I try to
eliminate duplicates, but at least in Brave it doesn't work well, so you
end up with duplicate entries). Here, it should be enough to reorder the
calls (open the camera stream first, then populate the menus). Oh well,
another item for my todo list.
-- Juliusz
next prev parent reply other threads:[~2026-09-06 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 14:00 [Galene] ANNOUNCE: Galene 1.2 Juliusz Chroboczek
2026-09-05 20:30 ` [Galene] " Toke Høiland-Jørgensen
2026-09-06 9:32 ` Juliusz Chroboczek [this message]
2026-09-07 10:37 ` Toke Høiland-Jørgensen
2026-09-07 13:08 ` Juliusz Chroboczek
2026-09-07 14:10 ` Toke Høiland-Jørgensen
2026-09-07 15:22 ` Juliusz Chroboczek
2026-09-07 16:01 ` Toke Høiland-Jørgensen
2026-09-06 12:28 ` Kenichiro Matohara
2026-09-07 15:27 ` Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ecf6d8so.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=toke@toke.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox