From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] Re: if((c = t.style.color)
Date: Mon, 17 Jun 2019 22:50:20 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1906172243350.58325@carhart.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1906172210170.58325@carhart.net>
Actually I misread the error message a little. If it reports could not
get color of undefined, that means that the elements do not have a style
object, not that they don't have a color property. I echoed nodeType and
found out that the two elements where this happens are comment and H1.
For the comment, could we add a style at
roughly 1380? As for the H1, I don't know, do these headings get treated
similar to the paragraph P? Maybe there is a different solution to this
altogether. It can't be happening that often or there would be a lot of
errors in eb$visible.
next prev parent reply other threads:[~2019-06-18 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 5:16 [edbrowse-dev] " Kevin Carhart
2019-06-18 5:50 ` Kevin Carhart [this message]
2019-06-18 9:28 ` Karl Dahlke
2019-06-24 4:06 ` 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.1906172243350.58325@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).