From: "Valent@MeshPoint" <valent@meshpointone.com>
To: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] CSS cleanup
Date: Sun, 04 Oct 2026 14:33:24 +0000 [thread overview]
Message-ID: <em96a6b0e0-93c1-46c1-87ef-7ff5b8135952@meshpointone.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Hi Juliusz and list,
I started to clean up the CSS. Let me know if this PR makes sense as a
first step: it groups all z-index values in one place, so they're not
scattered all over galene.css:
https://github.com/jech/galene/pull/337
I also sent a second one for the sidebarnav. Its width was set in the
.js file, so I moved it into galene.css so all numbers for adjusting the
UI/UX experience is in one place:
https://github.com/jech/galene/pull/338
I tested both patched independently and then together, but test them
also on your systems.
Any comments and constructive feedback is welcome.
Best regards,
Valent
[-- Attachment #2: Type: text/html, Size: 1843 bytes --]
reply other threads:[~2026-10-04 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em96a6b0e0-93c1-46c1-87ef-7ff5b8135952@meshpointone.com \
--to=valent@meshpointone.com \
--cc=galene@lists.galene.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