From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] spec > highspec
Date: Sun, 2 Jun 2019 19:03:10 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1906021851050.185757@carhart.net> (raw)
I'm not sure if I found the answer to the baseball display problem, or
just a truism.
Suppose that the specificity check at line 3044 of css.c
read spec > highspec instead of spec >= highspec?
I tracked down several sets of display:block that don't get applied, and
when they don't get applied, spec=highspec. Loosen the threshhold by 1,
and you get a lot of content.
next reply other threads:[~2019-06-03 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 2:03 Kevin Carhart [this message]
2019-06-03 4:10 ` Karl Dahlke
2019-06-03 4:25 ` Kevin Carhart
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=alpine.DEB.2.21.1906021851050.185757@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.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).