From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] defaultView and getComputedStyle patch
Date: Mon, 14 Aug 2017 20:05:45 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1708141935570.4280@carhart.net> (raw)
In-Reply-To: <20170714212607.eklhad@comcast.net>
If I understand correctly, I think you can't have too much dynamism or
dynamicness. Does CSSStyleDeclaration get you something that style does
not? Maybe so, if we write it that way. Does CSSStyleDeclaration hinder
you from something that style gives you? I don't think so. Are there any
drawbacks?
On Mon, 14 Aug 2017, Karl Dahlke wrote:
> So CSSStyleDeclaration is a class that spins off objects.
> Is it possible that every one of our style objects, that we create under nodes, should be an instance of CSSStyleDeclaration, rather than Object?
> So under an anchor tag, or I should say the anchor object, we create style as an instance of CSSStyleDeclaration,
> then link element back to the anchor object so we know where it came from.
> anchorObj.style.element = anchorObj;
> And I don't know about style, maybe that links to itself.
> style.style = style;
> Then your getComputedStyle(e) can indeed return e.style and everything works.
> I don't know if this is how it's suppose to work, but I bet it would pass all the tests.
>
> Karl Dahlke
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2017-08-15 3:05 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 [this message]
[not found] ` <20170715003928.eklhad@comcast.net>
2017-08-15 5:38 ` Kevin Carhart
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.1708141935570.4280@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).