Yes, this is a dhtml issue. InfoView is part of the larger packages - Crystal Server, Crystal Enterprise, and BusinessObjects Enterprise. They all default to the dhtml viewer, so they will have the same problem.
I'm not sure that it's possible to resolve this issue in the web version of the CrystalReportViewer component, but I'm sure someone will correct me if I'm wrong.
An alternative might be to export the report to a PDF and then display that instead of the report. This option is only valid if you're not doing any drill-downs and it has its own set of challenges.
-Dell