From: Rito Rhymes via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Rito Rhymes <rito@ritovision.com>
Subject: [FFmpeg-devel] [PATCH v2 0/2] rework mobile navigation
Date: Mon, 9 Feb 2026 15:04:05 -0500
Message-ID: <20260209200407.13956-1-rito@ritovision.com> (raw)
The mobile sidebar pushes page content right, causing page-wide
horizontal scroll overflow. Users also cannot close it without
scrolling back to the top to reach the hamburger icon.
v1 attempted to fix this by making the sidebar into a fixed
overlay but was rejected for not allowing the user to effectively
read or scroll page content while opened; it covered part of the
content width, cutting off lines of text mid-sentence.
v2 takes a different approach, replacing the sidebar with a
bottom drawer, allowing users to read and scroll page content
while the menu is visible.
Patch 1 replaces the sidebar with a bottom drawer on mobile.
Patch 2 (optional) makes the content header sticky so the
humburger icon / drawer toggle is always reachable.
Rito Rhymes (2):
web: replace mobile sidebar with bottom drawer
web: make content header sticky on mobile
htdocs/css/simple-sidebar.css | 105 +++++++++++++++++++++++++++++++---
src/template_footer2 | 29 +++++++++-
src/template_head2 | 7 +++
3 files changed, 130 insertions(+), 11 deletions(-)
--
2.51.0
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next reply other threads:[~2026-02-09 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 20:04 Rito Rhymes via ffmpeg-devel [this message]
2026-02-09 20:04 ` [FFmpeg-devel] [PATCH v2 1/2] web: replace mobile sidebar with bottom drawer Rito Rhymes via ffmpeg-devel
2026-02-09 20:04 ` [FFmpeg-devel] [PATCH v2 2/2] web: make content header sticky on mobile Rito Rhymes via ffmpeg-devel
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=20260209200407.13956-1-rito@ritovision.com \
--to=ffmpeg-devel@ffmpeg.org \
--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