From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] setAttribute
Date: Tue, 06 Oct 2015 20:10:20 -0400 [thread overview]
Message-ID: <20150906201020.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1510061641040.12804@carhart.net>
> It seems like people are saying that dot notation is
> actually preferred and is a superset of setAttribute.
Yes so it seems, so I have to query variables as needed anyways,
so no need for setAttribute to do anything more than
function setAttribute(s,t) { this[s] = t; }
I may implement it this way and get rid of the corresponding
20 line native code.
As mentioned last time, I check for form.action before submit,
but I don't check to see if js changed the href=
attribute out from under you before you click on hyperlink.
There's probably quite a few of these "actions" that I don't check for
and should.
Karl Dahlke
next prev parent reply other threads:[~2015-10-07 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 17:43 Karl Dahlke
2015-10-06 23:51 ` Kevin Carhart
2015-10-07 0:10 ` Karl Dahlke [this message]
2015-10-07 2:26 ` Chris Brannon
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=20150906201020.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).