edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] questions about new finds
Date: Sun, 3 Jul 2016 09:54:19 +0000	[thread overview]
Message-ID: <20160703095419.GA19967@odin> (raw)
In-Reply-To: <20160602132935.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On Sat, Jul 02, 2016 at 01:29:35PM -0400, Karl Dahlke wrote:
> > What do we do in the first case, i.e. if we get <unknowntag>?
> 
> When tidy sees <foobar> it says "discarding unknown tag".
> This may prove to be an unacceptable behavior at some point.
> A lot depends on what other browsers do with it,
> and whether we are expected to do the same.

But these aren't unknown tags in tidy since they're html5, they're just unknown in Edbrowse.  I'm wondering if there's anything we can do in the meantime whilst
we get our html5 support completed to at least provide the html5 stuff as part of the DOM for use by js.  Any ideas?  I think that header, footer (probably
comment and fragment too) should be treated like div in edbrowse, and probably same for article (and it's subtags) but obviously js needs to see the original
element types.  From memory there are a few more div-like tags as well though I can't remember what they are without going through the spec.
<video> is for embedding video files and, I think, <canvas> is some sort of drawing element though I don't know what it does (or if it can be used) with text.

Cheers,
Adam.

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-03  9:54 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
2016-07-02 17:29       ` Karl Dahlke
2016-07-03  9:54         ` Adam Thompson [this message]
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=20160703095419.GA19967@odin \
    --to=arthompson1990@gmail.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.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).