HTML Report minification

an idea:

we have done a simple implementation, not implemented but they support data loading on scroll - as you suggested - and many plugins. I Assume for a complex implementation need analysis and design from core team.

As it is, this is fine to goes into trunk.

As per my experience, a large html report (a few mb+) is just not viewable/usable on browser (even after minify) and a real solution will have to split that to multiple pieces (each piece must < 1mb) and we will have to build a viewer at font end that can handle that (paging/scrolling through the available pieces).

Just as a note: I tried tidy on both reports and the output was the same except the style part that is restored as CDATA (just spaces added in the non-minified version).

Anyways I agree with suggestion, a SysConfig to turn minification off (so, minification on by default) can be useful if we encounter some unexpected result in any report.

Regards,

Carlos Ruiz

I guess we might need a setting that can turn this off. This would be a problem for user that want to edit/post process the html report (it is not readble).

Don’t forget about DOM objects. we learned lot around mobile ionic development and each byte count.

The reason why we are investigate is because our 8.2 is slowdown after 3-4 hours works.

This can be caused DOM issues, so i assume less data, less count of DOM tree objects should help.

Let me ask what you think about another idea - move css class generator - own - or sass, less. which means much more saving. see example html file.

let me know this made much more saving in kb.(delete classes from td and use nth feature of css.)

norbert