Yes, but it is loaded with notes from my work here at Facebook, so I have
to trim it down to a minimal repro. I started on that yesterday, but it is
a large file and I find that if I cut out certain parts of it, the problem
goes away . . . :-P
I should have something for you tomorrow or Thursday.
Thanks for responding. Marked2 is a great product . . . I also enjoy your
twitter feed BTW.
Brett on 10 Apr, 2018 03:18 PM
Sure. All I'm interested in is what part of it is causing a JS error. If
you know that removing a certain part fixes it, and loading just that
certain part happens to reproduce it, you could just redact that part
and send it to me. All I need is a way to replicate the issue.
Brett on 12 Apr, 2018 08:35 PM
Yep, because both of those open up HTML tags that then encompass
succeeding elements in the DOM because they're never closed. If you
escape the angle brackets or wrap them in backticks, the problem should
go away. This seems a reasonable solution since in their current format
they wouldn't render as intended anyway.
Brett on 12 Apr, 2018 09:26 PM
It's a fair point, but because the TOC is generated from the DOM, the
script itself has no concept of whether the DOM is rendering the
original content correctly or not. It could fail more gracefully, yes,
but it has to deal with almost _completely_ unpredictable markup
scenarios and in a lot of cases it doesn't appear as a failure so much
as an index of invalid display elements. I'm just saying it's a tricky
area when providing useful feedback :).