Preview
Issue #3
No IV
- Andrew A.
- It's a source issue—first; it's an IV issue—second; your fix is meaningless—third.
Why it's a source issue: the layout of this page is corrupt, and corrupt badly. There are <p>s as direct descendants of <ul> (outside of <li>), there is an unclosed <ul> and unclosed last <li>, there is a closing </p> (after "interceptions.") without an opening <p>. Crashing in such conditions makes total sense.
Why it's an IV issue: this page crashes with the "<img> nested in <p>" error. However, my template does all necessary routines to overcome this nestation, and the resultant code contains no <img> inside <p>. The error seems to happen inside the @simplify function, probably when it tries to make sense of one of the errors I listed above.
Why your fix is meaningless: in fact, you freely transform the DOM by moving <p>s to preceding <li>s. You apply a very specific fix on one page, but it doesn't have any global significance, and there can be any other kind of broken HTML on pages—we can't and shouldn't fix it all.
- Declined by admin
- Type of issue
- IV not generated for target page
- Reported
- Apr 30, 2019