From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>, Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] defaultView and getComputedStyle patch
Date: Mon, 14 Aug 2017 22:38:53 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1708142233400.27032@carhart.net> (raw)
In-Reply-To: <20170715003928.eklhad@comcast.net>
I agree! Sorry, I was being sort of rhetorical! I should have said,
it's a good idea because blah blah, CSSStyleDeclaration is a superset of
style so it's good on all cylinders.
Where does it live, and how should we do it? Is it JS, or is it back in
decorate?
If you have time and stamina, I would like to keep going from this, to
what is actually going wrong when it goes through the motions in test
zero. It can't be that difficult. It is just some DOM maneuvers, but I
think I have noticed something wrong with which scripts are found in head,
or body. It's great that we're banging this out. Could you run those
first three or four lines in case something will leap out at you that
doesn't leap out at me?
On Tue, 15 Aug 2017, Karl Dahlke wrote:
>> Does CSSStyleDeclaration get you something that style does not?
>
> Sure. All the methods of CSSStyleDeclaration.
> Like if js ever calls
> some_element.style.getPropertyValue("foo");
> Etc.
>
> Karl Dahlke
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2017-08-15 5:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 4:42 Kevin Carhart
2017-08-14 6:35 ` Karl Dahlke
2017-08-15 0:48 ` Kevin Carhart
2017-08-15 1:26 ` Karl Dahlke
2017-08-15 3:05 ` Kevin Carhart
[not found] ` <20170715003928.eklhad@comcast.net>
2017-08-15 5:38 ` Kevin Carhart [this message]
2017-08-15 6:43 ` Karl Dahlke
2017-08-15 7:08 ` Kevin Carhart
2017-08-15 7:33 ` Kevin Carhart
2017-08-15 8:33 ` Karl Dahlke
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.LRH.2.03.1708142233400.27032@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).