edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] getAttributeNode / setAttributeNode
Date: Mon, 21 Aug 2017 16:01:52 -0400	[thread overview]
Message-ID: <20170721160152.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1708211155420.12268@carhart.net>

[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]

Ok I now convert foo-bar to fooBar, as you suggest, and as the acid test 0 suggests, but I think it's wweird.

You say you're not finding the right properties in penultimate, but oh boy it's very subtle.
There are several problems at play.
The selector we're looking for is #instructions:last-child, and I had to read some of the MIT code to see what that meant.
It means the node with id=instructions, and it has to be the last nontrivial child of its parent, where nontrivial beans nodeType = 1.
So a silly empty whitespace node doesn't count.
At the time the acid test runs, and at the time it calls getComputedStyle() to make its calculation,
it has already removed the paragraph after instructions, and the instructional paragraph is indeed the last child of its parent.
So getComputedStyle creates a style object for this node, and it should have whiteSpace set properly, but it's just a dynamically created style node, it's not the actual style attached to the node.
That style we might be messing with, might change it to green etc.
getcomputedStyle simply tells you what the style would be, right now, if all the rules were applied.
So I'm starting to unravel that but there's another problem.
After this test runs, and succeeds or fails, another script runs and does a document.write which adds all sorts of nodes to body.
So now the browse is done, and you get into jdb, and you try to reproduce this stuff, but you can't,
because instructions isn't the last child of its parent any more.
It was but it isn't any more, so the machinery looks like it's not working but it works just fine.

So - I think we are just one step away from test 0 passing.
The test expects a blank node between the two paragraphs, a node corrresponding to the newline character, an empty node, a node of nodeType 0,
but tidy doesn't give us this node, so nothing lines up.
I asked Geoff about this and am waiting for his reply.
If tidy doesn't give us those nodes, then acid test 0 will never pass.

Karl Dahlke

  reply	other threads:[~2017-08-21 20:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 15:38 [Edbrowse-dev] acid[0] Karl Dahlke
2017-08-19 22:53 ` Kevin Carhart
2017-08-19 23:08   ` Karl Dahlke
2017-08-19 23:33     ` Kevin Carhart
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 [this message]
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=20170721160152.eklhad@comcast.net \
    --to=eklhad@comcast.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).