From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] attributes
Date: Sat, 29 Jun 2019 19:08:58 -0400 [thread overview]
Message-ID: <20190529190858.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1906291245270.225792@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
I could use your help here.
Line 1680 is there because acid test 17 says that getAttribute of id should not return the id unless it was set by setAttribute, or that is the way I interpreted it at some point.
These various implicitMember functions are suppose to be exceptions, times when you don't getAttribute unless you did an earlier setAttribute.
Same for "class" acid test 61.
Maybe I'm not interpreting the acid tests right,
maybe I just need someone else to take a second look.
I have acid3 in the github source, it is my version of the original page, but I think it is true to that page, with my comments and changes of course.
Karl Dahlke
next prev parent reply other threads:[~2019-06-29 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 20:21 Kevin Carhart
2019-06-29 23:08 ` Karl Dahlke [this message]
2019-06-30 1:14 ` 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=20190529190858.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).