On 20/08/15 01:21, Erwin Dokter wrote:
I mentioned this once before:
http://www.htacg.org/tidy-html5/
While Tidy died in 2008, this fork lives on and is HTML5 aware. That will at least solve a lot of problems *caused* by Tidy, such as not allowing block elements inside inline elemensts (which is allowed in HTML5).
Can we at least evaluate if this is a suitable interim solution?
That's not a solution to the problems that we are trying to solve.
As I said in my original post, my number one problem with Tidy is that it changes. So I am very happy that it is not in active development. Switching to a fork that is actively maintained would be much worse. It would be like the switch from Tidy to the proposed HTML reserializer web service, except that the pain would be repeated every time we upgrade our Linux distribution.
The other problem with Tidy is that it is poorly specified and has only one implementation. Switching to a fork of it doesn't improve the situation.
HTML 5 has not significantly relaxed the rules about block elements inside inline elements. The terminology has changed: now instead of inline elements we have "phrasing content" and instead of block elements we have "flow content". You're still not allowed to put a <div> inside a <span>, because <span> is phrasing content and <div> isn't.
The "children" column here has a summary:
http://www.w3.org/TR/html5/index.html#elements-1
-- Tim Starling