Regardless of the method (to which I would defer to your expertise), I would personally prefer the outcome you described in the latter post: namely the Reports feature only running when all xhtml is strictly valid. That would (or should) avoid both the crashing and the potential for the modification of underlying code merely to be able to run the reports.
Have said that, however: I'm not one who really uses the Reports feature. We should probably get the opinions of some who use it regularly. Massage invalid code (invalid by strict xhtml rules) to allow Reports to run without crashing, or not allow Reports to be run when there's strictly invalid xhtml present. Assuming I've interpreted the gist of your propositions accurately, of course.
Last edited by DiapDealer; 09-27-2018 at 05:03 PM.
|