user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Cc: Dmitry Alexandrov <321942@gmail.com>,
	Mateusz Loskot <mateusz@loskot.net>
Subject: [PATCH 0/2] ensure user CSS always overrides BOFH CSS
Date: Sat, 23 Feb 2019 10:56:36 +0000
Message-ID: <20190223105638.15465-1-e@80x24.org> (raw)
In-Reply-To: <20190223024712.qcvjsnnwzfzxp3az@dcvr>

First, ensure our sample CSS includes "!important" to override
what the BOFH set.

Then, make sure BOFHs can't set "!important" to override
what users set in their private CSS files.

Thanks to Dmitry Alexandrov <321942@gmail.com> for noticing
this.

Eric Wong (2):
  usercontent.pm: set "!important" to override BOFH prefs
  www: prevent '!important' in BOFH-specified CSS

 lib/PublicInbox/UserContent.pm | 41 +++++++++++++++++++++-------------
 lib/PublicInbox/WWW.pm         | 12 ++++++++--
 2 files changed, 35 insertions(+), 18 deletions(-)

-- 
EW


  reply index

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 13:36 Default theme Mateusz Loskot
2019-02-22  8:50 ` Eric Wong
2019-02-22 20:39   ` Dmitry Alexandrov
2019-02-23  2:47     ` Eric Wong
2019-02-23 10:56       ` Eric Wong [this message]
2019-02-23 10:56         ` [PATCH 1/2] usercontent.pm: set "!important" to override BOFH prefs Eric Wong
2019-02-23 10:56         ` [PATCH 2/2] www: prevent '!important' in BOFH-specified CSS Eric Wong
2019-02-23 19:55       ` Default theme Mateusz Loskot
2019-02-22 20:53   ` Mateusz Loskot
2019-02-23  1:19     ` Dmitry Alexandrov
2019-02-23  2:50       ` Eric Wong
2019-02-23 10:49         ` Eric Wong

Reply instructions:

You may reply publically 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: http://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190223105638.15465-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=321942@gmail.com \
    --cc=mateusz@loskot.net \
    --cc=meta@public-inbox.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

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror http://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.org/gmane.mail.public-inbox.general

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox