edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] acid[0]
Date: Sat, 19 Aug 2017 16:33:21 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1708191628190.14247@carhart.net> (raw)
In-Reply-To: <20170719190803.eklhad@comcast.net>

On Sat, 19 Aug 2017, Karl Dahlke wrote:

> Well duktape has some json support out of the box.
> It has a JSON global object, with JSON.parse() in it and I don't know what else, so using js to convert css to json might be a practical pathway.

Correction:  Actually I made a mistakes that it was JSON.  The 
parser doesn't return JSON, the parser returns a tree of nested objects. 
The documentation simply turned it into JSON in order to serialize the 
contents of the object for readability.  So this is even more familiar, 
just traversal with recursion maybe.

> Course we'd have to follow up with a function to apply bgcolor=white to 
> foo.style wherever that makes sense.

I think that's right.  We might get the first two thirds of a three step
process done "free" by the libraries and have to write the function that
you describe.  Since querySelectorAll returns elements (foo) and the
parser css.js breaks down selectors, attribute names (bgcolor) and
attribute values (white) into neat compartments, I think it would be
(don't want to speak too soon) somewhat straightforward to dole out
bgcolor=white to foo.style.

Here is the code for the parser and then for querySelector:

https://raw.githubusercontent.com/jotform/css.js/master/css.js
https://raw.githubusercontent.com/yiminghe/query-selector/master/build/query-selector-debug.js

And here are the git projects:

https://github.com/jotform/css.js.git
https://github.com/yiminghe/query-selector.git

K

  reply	other threads:[~2017-08-19 23:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 15:38 Karl Dahlke
2017-08-19 22:53 ` Kevin Carhart
2017-08-19 23:08   ` Karl Dahlke
2017-08-19 23:33     ` Kevin Carhart [this message]
2017-08-20  0:00       ` Karl Dahlke
2017-08-20  0:37         ` Kevin Carhart
2017-08-20 14:33           ` Karl Dahlke
2017-08-20 20:00             ` Kevin Carhart
2017-08-20 20:08               ` [Edbrowse-dev] getAttributeNode / setAttributeNode Kevin Carhart
2017-08-20 20:24                 ` Karl Dahlke
2017-08-20 20:56                   ` Kevin Carhart
2017-08-20 21:59                     ` Kevin Carhart
     [not found]                       ` <20170721105041.eklhad@comcast.net>
2017-08-21 19:11                         ` Kevin Carhart
2017-08-21 20:01                           ` Karl Dahlke
2017-08-24  9:54                             ` Kevin Carhart
2017-08-24  9:57                             ` Kevin Carhart
2017-08-25  8:19                             ` Kevin Carhart
2017-08-25 22:09                               ` [Edbrowse-dev] whitespace nodes Kevin Carhart
2017-08-25 22:56                                 ` Karl Dahlke
2017-08-26  4:25                                   ` [Edbrowse-dev] (something other than) " Kevin Carhart
2017-09-02  9:03                                     ` Adam Thompson
2017-09-02 15:42                                       ` 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.1708191628190.14247@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).