From: Karl Dahlke <eklhad@comcast.net>
To: ubuntu@geoffair.info, edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] <table> <form>
Date: Thu, 22 Dec 2016 13:35:44 -0500 [thread overview]
Message-ID: <20161122133544.eklhad@comcast.net> (raw)
In-Reply-To: <4449751f-0582-add8-0cb0-74ff1d69c97f@geoffair.info>
> And yes, tidy will see that as invalid html!
And that's fine.
> tidy will close the form, move the script out of the table,
In an ideal world, from our point of view, it would still leave the form open.
There is a </form> later on down the page.
If tidy just can't do that, I could think about postprocessing the tree,
moving the nodes to the right of the form down to children of the form,
or some such, but every time I've tried to postmuck with the tree
I've fixed one web page and broken 8 others.
So I'm not fond of going down that path.
Karl Dahlke
next prev parent reply other threads:[~2016-12-22 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 19:14 Karl Dahlke
2016-12-21 14:01 ` Chris Brannon
2016-12-21 17:03 ` Geoff McLane
2016-12-22 18:35 ` Karl Dahlke [this message]
2016-12-22 20:13 ` Geoff McLane
2016-12-25 12:53 ` Adam Thompson
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=20161122133544.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=ubuntu@geoffair.info \
/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).