From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] allocating <SCRIPT> to <HEAD> or <BODY>
Date: Thu, 02 Mar 2017 22:24:36 -0500 [thread overview]
Message-ID: <20170202222436.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1703020919420.5244@carhart.net>
Well that funny script compiles pretty well on my system, no errors just warnings.
The three frames are there, I assume the third would expand properly if we were running this on their site.
But a question:
<iframe>stuff</iframe>
What am I suppose to do with stuff?
Right now it appears after the frame.
On a standard browser you might not see it at all,
the frame sitting on top of it.
Karl Dahlke
prev parent reply other threads:[~2017-03-03 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 2:43 Kevin Carhart
2017-03-02 12:00 ` Karl Dahlke
2017-03-02 18:11 ` Kevin Carhart
2017-03-02 19:56 ` Chris Brannon
2017-03-03 3:24 ` 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=20170202222436.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).