View Single Post
Old 11-14-2015, 06:45 PM   #77
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi DiapDealer,

Quote:
Originally Posted by DiapDealer View Post
Out of curiosity, do we know if Sigil's previous well-formed check just ignored this (since the functionality of the button obviously hasn't changed)?
I have no idea. I don't even know if flightcrew picks it up or not. The issue is gumbo is adhering to the rules while Qt seems to be more generous in what it accepts.

I did try the same code in the latest Firefox, and then fired up Developer in Firefox and examined the code source and sure enough the final </p> is given in red meaning it is an error because the browser implicitly closed the first p when it saw the ul tag, leaving a closing p tag without a paired opening one.
This is the exact same error message that gumbo reports.

So if software using Webkit doesn't handle it properly now, it probably will in some future release. I have not tried in in Safari yet.

Kevin
KevinH is online now