Gisle Aas wrote:
> > Seems like a correct fix. I'll make sure it makes it into the next
> > HTML-Parser release.
>
> No, I will not after all. I think I agree with Tim Allwine's comment
> and will consider the current behaviour as it should be. There is
> probably also code out there that rely on the current behaviour.
Just fine with me, but *please* keep in mind that the documentation
seems to point to a different behaviour, or is, at least, a tad
confusing. If you won't patch the code (and I find it reasonable that
you respect backward compatibility), at least do patch the
documentation.
As a last request, and as I'm not in [EMAIL PROTECTED], could you either
forward Tim's post to me, or point me to the list archives? It looks
like I've spawned an interesting thread, and I haven't been aware of it
...
martin
