Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Rito Rhymes via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
	Rito Rhymes <rito@ritovision.com>
Subject: [FFmpeg-devel] Re: [PATCH] prevent sidebar from causing horizontal page scroll on mobile
Date: Tue, 17 Feb 2026 15:46:39 -0500
Message-ID: <DGHJ5190WVIJ.R38QQ7TWTXV3@ritovision.com> (raw)
In-Reply-To: <aYnMO7817j6xkLQA@neo>

I realized I mistakenly sent an HTML reply the other 
week to this, so it may have gotten lost.

What I meant to say was, thank you for the feedback
and insight on your vision for the navigation interface.

I already sent a new patch series that implements a
bottom drawer UI architecture to effectively address
both:
1) the concern you raise about not being able to read 
and navigate page content while a menu is opened, and 
2) the a11y concern I raised about page overflow behavior
(for the current sidebar when opened).

I wanted to know if you preferred this direction or an 
alternative one; I decided to send a working series 
so you can see what it's like to use.

If you have any other specific requirements or possible 
features in mind that could be added to improve the mobile 
experience or navigation in general, do share.

-Rito
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      parent reply	other threads:[~2026-02-17 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 12:26 [FFmpeg-devel] " Rito Rhymes via ffmpeg-devel
2026-02-09 11:59 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2026-02-09 13:03   ` Matthew Pellerito via ffmpeg-devel
2026-02-17 20:46   ` Rito Rhymes via ffmpeg-devel [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DGHJ5190WVIJ.R38QQ7TWTXV3@ritovision.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    --cc=rito@ritovision.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git