- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 2 Oct 2014 15:00:46 -0400
- To: Tobie Langel <tobie.langel@gmail.com>
- Cc: Peter Linss <peter.linss@hp.com>, Robin Berjon <robin@w3.org>, Shane McCarron <shane@aptest.com>, "spec-prod@w3.org Prod" <spec-prod@w3.org>
On Thu, Oct 2, 2014 at 2:57 PM, Tobie Langel <tobie.langel@gmail.com> wrote: > On Thu, Oct 2, 2014 at 7:08 PM, Peter Linss <peter.linss@hp.com> wrote: >> On Oct 2, 2014, at 4:41 AM, Tobie Langel <tobie.langel@gmail.com> wrote: >>> I've bumped into way too many painful issues with non browser-based HTML >>> parsers to waste more time with them. >> >> FWIW, Shepherd uses html5lib and AFAICT sees a browser equivalent DOM >> which it traverses. This hasn’t been an issue to date. > > So does jsdom[1]. Yet I've bumped into plenty of very annoying issues with > it (even though jsdom actually has a JS runtime, which afaik html5lib > doesn't). Huh. I've never run into any problems, myself. ~TJ
Received on Thursday, 2 October 2014 19:01:40 UTC