The demo Web viewer generates a javascript error in Chrome. Haven't tried IE yet. This error also occurs in my web app when I use the web forms viewer.
It doesn't seem to cause a problem showing the report, but it is still an error in the console none the less. The attached is a screen shot of the Chrome debugging console. This is the first pass through this function. There's a second pass through that succeeds with an actual valid URL to the .axd handler to, presumably, render the report in the iframe. However, why on the first pass are you trying to load the iframe from javascript:void(0);&RenderID= ?
Just to clarify, this is the demo c# solution, setting the WebDemo as the startup project.
It doesn't seem to cause a problem showing the report, but it is still an error in the console none the less. The attached is a screen shot of the Chrome debugging console. This is the first pass through this function. There's a second pass through that succeeds with an actual valid URL to the .axd handler to, presumably, render the report in the iframe. However, why on the first pass are you trying to load the iframe from javascript:void(0);&RenderID= ?
Just to clarify, this is the demo c# solution, setting the WebDemo as the startup project.
1 Answer, 1 is accepted
0
Hello Chris,
We're aware of this error and it is inherent to web kit based browsers. As far as we know everything works in the viewer, despite of the error so you should not worry. For Q3 2011 we're working on a new report layout optimized for screen-based report viewing that would be [let's call it] "browser irrelevant" and we hope that this problem would simply cease to exist. You can read more about the new features in the Roadmap, which we posted a few weeks ago.
Regards,
Steve
the Telerik team
We're aware of this error and it is inherent to web kit based browsers. As far as we know everything works in the viewer, despite of the error so you should not worry. For Q3 2011 we're working on a new report layout optimized for screen-based report viewing that would be [let's call it] "browser irrelevant" and we hope that this problem would simply cease to exist. You can read more about the new features in the Roadmap, which we posted a few weeks ago.
Regards,
Steve
the Telerik team
Q2’11 SP1 of Telerik Reporting is available for download (see what's new). Get it today.