From: Maxime Devos <maximedevos@telenet.be>
To: me@tobias.gr, 55625@debbugs.gnu.org, roman@riabenko.com
Subject: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 18:29:18 +0200 [thread overview]
Message-ID: <ac742afd32bf9e616a4004c83d007c62e374661b.camel@telenet.be> (raw)
In-Reply-To: <7AFB0B2E-0699-41DF-8A45-58E6BA41133B@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Tobias Geerinckx-Rice schreef op za 28-05-2022 om 15:35 [+0000]:
> 'Accessible' just means 'available' (toeganklijk, same problem though).
>
> It does not generally imply 'accesibility' as used in various fields of engineering, although of course we're biased to read it so.
>
> Anyway, Maxime: do the buttons work for you once the codec's fixed? My computer seems to have frozen whilst building them.
Pressing the ‘pause’ buttons turns it into ‘play’ button and the other
way around.
The next chapter/movie button doesn't work, but the file that is
playing doesn't have any chapters, so not surprising. OTOH, there is
another .mp4 in the same directory.
The previous/next chapter are ‘accessible’ in the sense that they are
visible, the cursor could be moved on top of them and moving the cursor
above them displays a tiny popup, but they are unclickable.
I don't know what exactly was meant by accessibility (the existence of
the buttons or the pressability?) in the bug report.
There is some weirdness though:
* no sound (though that might be a problem in the played mp4 itself,
there were some recording problems)
* The pause/play button don't seem to have any effect apart from
toggling what the button looks like -- the played mp4 remains
frozen.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-28 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 6:03 bug#55625: GNOME: totem controls not accessible Roman Riabenko
2022-05-28 15:11 ` Maxime Devos
2022-05-28 15:35 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-05-28 16:29 ` Maxime Devos [this message]
2022-05-28 16:34 ` Maxime Devos
2022-05-28 19:15 ` Roman Riabenko
2022-05-28 19:28 ` Maxime Devos
2022-05-28 19:31 ` Maxime Devos
2022-05-30 18:45 ` Roman Riabenko
2022-05-28 15:20 ` Maxime Devos
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac742afd32bf9e616a4004c83d007c62e374661b.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55625@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=roman@riabenko.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).