From: Adam Thompson <arthompson1990@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Karl Dahlke <eklhad@comcast.net>, edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] questions about new finds
Date: Sat, 2 Jul 2016 16:48:33 +0000 [thread overview]
Message-ID: <20160702164833.GA13590@odin> (raw)
In-Reply-To: <alpine.LRH.2.03.1606262311350.11865@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Hi all,
First of all appologies for going silent for a while; work, life and computer issues basically.
On Sun, Jun 26, 2016 at 11:39:49PM -0700, Kevin Carhart wrote:
>
> >(1) Do you mean <modernizer> in the html text or createElement("modernizer")?
> >Those are radically different issues.
> >The first is up to tidy, and out of our hands.
What do we do in the first case, i.e. if we get <unknowntag>? If it's something we don't know are we putting it in the DOM but not rendering, or ignoring it?
Also, I think *some* of those tags are actually html 5 tags i.e. <video> and <canvas> (probably the header and comment also but can't remember) and thus we
should probably have some handling whether they're created in the html or via js (as in this case).
Cheers,
Adam.
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-02 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 11:22 Kevin Carhart
2016-06-23 16:41 ` Karl Dahlke
2016-06-27 6:39 ` Kevin Carhart
2016-07-02 16:48 ` Adam Thompson [this message]
2016-07-02 17:29 ` Karl Dahlke
2016-07-03 9:54 ` Adam Thompson
2016-07-02 22:11 ` Kevin Carhart
2016-07-03 11:12 ` 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=20160702164833.GA13590@odin \
--to=arthompson1990@gmail.com \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
--cc=kevin@carhart.net \
/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).