Re: [Edbrowse-dev] questions about new finds

[Kevin Carhart <kevin@carhart.net>]

Hi Adam and Chris,

There's a lot to do basically.  I see tidy errors, but I gravitate to the 
JS errors, I guess partially because they are autonomous for us to fix, 
while messages from tidy involve making threads with the tidy developers, 
fun and worthy in its own right, but the path of least resistance takes 
you to something you can work on right away.  (Dang, here's a toast to the 
tidy group!  It underpins everything now and it's so good I don't think 
about it!  We only integrated tidy around 1 year ago.)

We could add things to availableTags one by one as we find them but this 
will go forever.  I experimented adding a "placeholder" to availableTags 
and editing html.c so that if the call to newTag fails to find a string,
it will create your element as a "placeholder."  But I don't know what I'm 
doing - I was also seeing some infinite loops in renderNode, which I 
probably caused by adding placeholder.  I don't know what the TAGACT or 
flags should be for a made-up placeholder.

K



On Sat, 2 Jul 2016, Adam Thompson wrote:

> 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.
>

--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists