From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] document.removeAttribute
Date: Fri, 20 Jan 2017 19:27:53 -0500 [thread overview]
Message-ID: <20170020192753.eklhad@comcast.net> (raw)
In-Reply-To: <20170119200417.GA5912@odin>
I think most people just push and hope for the best, or run diff and send the patch around for review.
I'm guessing the page came out blank before, and still comes out blank, with subsequent js still not running,
so that what you did didn't "break" anything, but actually moves us forward.
If so then you should just push it, or use diff and show us a patch if you're feeling cautious.
Karl Dahlke
prev parent reply other threads:[~2017-01-21 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 20:04 Adam Thompson
2017-01-19 20:32 ` Chris Brannon
2017-01-19 21:34 ` Kevin Carhart
2017-01-24 8:43 ` Adam Thompson
2017-01-24 19:08 ` Adam Thompson
2017-01-24 20:48 ` Karl Dahlke
2017-01-24 22:08 ` Kevin Carhart
[not found] ` <20170024174651.eklhad@comcast.net>
2017-01-24 23:57 ` Kevin Carhart
2017-01-25 1:50 ` Karl Dahlke
2017-01-21 0:27 ` Karl Dahlke [this message]
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=20170020192753.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).