From: "Rito Rhymes" <rito@ritovision.com>
To: "Konstantin Ryabitsev" <mricon@kernel.org>,
"Rito Rhymes" <rito@ritovision.com>
Cc: <tools@kernel.org>
Subject: Re: [PATCH v1 0/6] Allow site layouts to render properly on mobile devices
Date: Mon, 03 Aug 2026 11:39:54 -0400 [thread overview]
Message-ID: <DKFF75A32GET.6XEQPMNNROK7@ritovision.com> (raw)
In-Reply-To: <20260803-inscrutable-graceful-bullfrog-df737b@meerkat>
I'm glad to see the series in action! And thanks for the follow up fix.
I just sent a follow-on two-patch series adding drawer navigation for
mobile, to round out the mobile experience. The second patch removes the
banner rules that become unreachable once the drawer hides #banner at
that breakpoint, including the nav clearance from your fix.
Rito
prev parent reply other threads:[~2026-08-03 15:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 18:00 [PATCH v1 0/6] Allow site layouts to render properly on mobile devices Rito Rhymes
2026-03-16 18:00 ` [PATCH v1 1/6] add viewport meta tag for proper mobile rendering Rito Rhymes
2026-03-16 18:00 ` [PATCH v1 2/6] prevent wrapped headings from overlapping with text above it Rito Rhymes
2026-03-16 18:00 ` [PATCH v1 3/6] add 848px mobile banner adjustments to prevent overflow Rito Rhymes
2026-03-16 18:00 ` [PATCH v1 4/6] add responsive extras and footer layout adjustments to contain overflow Rito Rhymes
2026-03-16 18:00 ` [PATCH v1 5/6] contain horizontal overflow in core content and homepage releases layout Rito Rhymes
2026-03-16 18:00 ` [PATCH v1 6/6] improve mobile rendering of docutils tables Rito Rhymes
2026-03-16 18:17 ` [PATCH v1 0/6] Allow site layouts to render properly on mobile devices Rito Rhymes
2026-03-30 2:08 ` Rito Rhymes
2026-04-10 2:42 ` Rito Rhymes
2026-04-10 13:59 ` Konstantin Ryabitsev
2026-04-11 13:12 ` Rito Rhymes
2026-05-19 9:51 ` Rito Rhymes
2026-07-16 13:52 ` Rito Rhymes
2026-08-03 13:11 ` Konstantin Ryabitsev
2026-08-03 15:39 ` Rito Rhymes [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=DKFF75A32GET.6XEQPMNNROK7@ritovision.com \
--to=rito@ritovision.com \
--cc=mricon@kernel.org \
--cc=tools@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).