From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: A less invasive cgit.css that works in an embedded environment?
Date: Sun, 28 Aug 2011 15:53:11 +0200 [thread overview]
Message-ID: <20110828135311.GA1448@blizzard> (raw)
In-Reply-To: <4E5854E5.2040502@azabani.com>
On Sat, Aug 27, 2011 at 10:22:29AM +0800, Delan Azabani wrote:
> Lukas Fleischer wrote:
> > Why don't you just embed the whole cgit body in a container and use
> > selectors [1], [2] to make the cgit styles match elements of the cgit
> > interface only?
> >
> > [1] http://www.w3.org/TR/CSS21/selector.html#descendant-selectors
> > [2] http://www.w3.org/TR/CSS21/selector.html#child-selectors
>
> Could you please elaborate on what you are suggesting? I'm not quite
> sure that I understand what I should do.
>
> The way I am seeing it so far, as the only output of cgit in
> embedded mode is <div id="cgit">...</div>, so it is already in a
> container.
>
> Should I just change all of the selectors in my copy of cgit.css to
> prepend #cgit?
Yes.
next prev parent reply other threads:[~2011-08-28 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 2:22 delan
2011-08-28 13:53 ` cgit [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-22 12:47 delan
2011-08-26 15:28 ` cgit
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=20110828135311.GA1448@blizzard \
--to=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).