[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] lss weirdness on <div class="contents"> (was Re: Why writ

From: Thomas Dickey
Subject: Re: [Lynx-dev] lss weirdness on <div class="contents"> (was Re: Why write new code for http 1.1 and 2.0)
Date: Wed, 30 Dec 2015 19:39:42 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Dec 30, 2015 at 09:58:52PM +0000, Thorsten Glaser wrote:
> David Niklas dixit:
> >Their are good ones out their like libcurl.
> Hm. Most of the text on e.g.
> is black on blue for me, and this is because of the
>       <div class="contents">
> (if I change it in content or contentx, the text becomes normal),
> but there’s no “contents” in either lynx.lss or AFAICT the source.
> Tom?

That's a feature... of the color-style (which usually is an improvement
over the non-color-style).

If you run a trace with everything turned on, you'll see a few lines:

        CSSPARSE:em.a => 3943 
        CSS(PA):style d=141 / h=3943, e=em.a
        => 4
        => 0
        parse_attributes 0/-1 4/-1 0
        CSS(SET): <em.a> hash=3943, ca=0x1000, ma=0x40000
        STYLE.start_element: <DIV>.<contents>, hcode=3943.
        CSS.CS:<em.a> style 3943 code 0xf67, color 0x1000
        CACHED: <em.a> @(1,0)
        CSS:LYAttrset color 0x1000 -> (black/blue)

That is, the combination of "div" and "contents" happens to match the
hashcode for "em.a".

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]