From: "Rito Rhymes via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Rito <rito@ritovision.com>, Rito Rhymes <rito@ritovision.com>
Subject: [PATCH v2 1/5] gitweb: add viewport meta tag for mobile devices
Date: Mon, 16 Feb 2026 15:53:27 +0000 [thread overview]
Message-ID: <ff85e97ceedd206f723061ced972b7b7ba431b56.1771257211.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2043.v2.git.1771257211.gitgitgadget@gmail.com>
From: Rito Rhymes <rito@ritovision.com>
Without a viewport meta tag, phone browsers render gitweb at desktop
width and scale the whole page down to fit the screen.
Add a viewport meta tag so the layout viewport tracks device width.
This is the baseline needed for mobile CSS fixes in follow-up commits.
Signed-off-by: Rito Rhymes <rito@ritovision.com>
---
gitweb/gitweb.perl | 1 +
1 file changed, 1 insertion(+)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index b5490dfecf..fde804593b 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -4214,6 +4214,7 @@ sub git_header_html {
<head>
<meta name="generator" content="gitweb/$version git/$git_version$mod_perl_version"/>
<meta name="robots" content="index, nofollow"/>
+<meta name="viewport" content="width=device-width, initial-scale=1"/>
<title>$title</title>
EOF
# the stylesheet, favicon etc urls won't work correctly with path_info
--
gitgitgadget
next prev parent reply other threads:[~2026-02-16 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 23:17 [PATCH 0/5] gitweb: fix broken mobile layouts across views Rito via GitGitGadget
2026-02-09 23:17 ` [PATCH 1/5] gitweb: add viewport meta tag for mobile devices Rito Rhymes via GitGitGadget
2026-02-09 23:17 ` [PATCH 2/5] gitweb: prevent project search bar from overflowing on mobile Rito Rhymes via GitGitGadget
2026-02-09 23:17 ` [PATCH 3/5] gitweb: fix mobile page overflow across log/commit/blob/diff views Rito Rhymes via GitGitGadget
2026-02-15 23:20 ` Eric Sunshine
2026-02-17 12:29 ` Matthew Pellerito
2026-02-09 23:17 ` [PATCH 4/5] gitweb: fix mobile footer overflow by wrapping text and clearing floats Rito Rhymes via GitGitGadget
2026-02-09 23:17 ` [PATCH 5/5] gitweb: let page header grow on mobile for long wrapped project names Rito Rhymes via GitGitGadget
2026-02-16 15:53 ` [PATCH v2 0/5] gitweb: fix broken mobile layouts across views Rito via GitGitGadget
2026-02-16 15:53 ` Rito Rhymes via GitGitGadget [this message]
2026-02-16 15:53 ` [PATCH v2 2/5] gitweb: prevent project search bar from overflowing on mobile Rito Rhymes via GitGitGadget
2026-02-16 15:53 ` [PATCH v2 3/5] gitweb: fix mobile page overflow across log/commit/blob/diff views Rito Rhymes via GitGitGadget
2026-02-16 15:53 ` [PATCH v2 4/5] gitweb: fix mobile footer overflow by wrapping text and clearing floats Rito Rhymes via GitGitGadget
2026-02-16 15:53 ` [PATCH v2 5/5] gitweb: let page header grow on mobile for long wrapped project names Rito Rhymes via GitGitGadget
2026-02-20 22:38 ` [PATCH v2 0/5] gitweb: fix broken mobile layouts across views Junio C Hamano
2026-02-21 0:17 ` Rito Rhymes
2026-02-22 8:39 ` Eric Sunshine
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=ff85e97ceedd206f723061ced972b7b7ba431b56.1771257211.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=rito@ritovision.com \
--cc=sunshine@sunshineco.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox