From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: Re: Cascading styles
Date: Thu, 25 Nov 2010 10:41:07 +0100 [thread overview]
Message-ID: <sa38w0hyc3w.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <m3tyj619o5.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 25 Nov 2010 02:20:10 +0100")
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Thu, Nov 25 2010, Lars Magne Ingebrigtsen wrote:
> will first make Foo white, and then black. So, er, either the overlays
> should be applied in reverse-stack-order, or `shr-insert-*-overlay'
> should avoid clobbering overlays that are already there, and that use
> the same properties (i.e., :foreground, etc).
Well I had the same problem with background. I resolved it by inserting
the background overlay with rear-advance.
But actually that's not a good fix since it will never stop advancing…
But I need it to be inserted before so the foregrounds will know what
the background is.
> So you'd inherit down into the DOM and pop when you exit. However,
> would that be correct? Er, no, not really. So you'd basically have the
> inline thing, plus the stylesheet, but not endlessly combining inline
> things.
I am missing the why. :)
> And I'm not sure this is worth doing... I mean, implementing it is
> probably easy, but computation-wise for the user...
I like it. It would be fun!
--
Julien Danjou
// ᐰ <julien@danjou.info> http://julien.danjou.info
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-11-25 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 1:20 Lars Magne Ingebrigtsen
2010-11-25 9:41 ` Julien Danjou [this message]
2010-11-26 1:16 ` Lars Magne Ingebrigtsen
2010-11-26 9:17 ` Julien Danjou
2010-12-05 13:14 ` Lars Magne Ingebrigtsen
2010-12-05 14:32 ` Lars Magne Ingebrigtsen
2010-12-06 11:21 ` Julien Danjou
2010-12-06 11:24 ` Lars Magne Ingebrigtsen
2010-12-06 15:12 ` Julien Danjou
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=sa38w0hyc3w.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--cc=ding@gnus.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).