Hi at all,
i've a problem with crystal report viewer, v. 13.0.2000.0. I'm upgrading a webapp using an older version 12 of CRV. So the reports are the same. Now displaying some of them they are half-hidden.
I've found that in this cases ther is an inline style opacity set to a low value. if i use the F12 instrument for IE9 and uncheck the attribute, the report is displayed correctly. Is there a bug of this version of CRV?
If you can provide detailed set of steps to reproduce the issue, including the design of the report, I'll try to reproduce the issue and see if this is a bug.
A link to a screeshot of the issue may also be helpful.
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]
Edited by: Ludek Uher on Nov 8, 2011 7:36 AM
With all due respect, I like to use the following analogy:
My Ferrari goes real good on the dirt road to my garage behind my house. Then I take it to a logging road and the thing bottoms out on every pot hole and eventually I loose the oil pan...
E.g.; use the product as per the supported platforms. IE 9 is not on that list, so don't use that road...
Maybe it runs using
meta id="FirstCtrlID" runat="server" http-equiv="X-UA-Compatible" content="IE=8"
but you need to place it at the top of the head section.
Some tests has a right result, i wait again..
ps: in the supported browser you have noticed IE7, but if i try to change the browser and the document mode to IE7, crviewer does not render properly reports: the white paper has a left offset and is half hidden .. !?
..these offset error does not exists in ie7 mode using crviewer 12..
..in the 13 release it seems caused by the element
div class="insetBorder" id="bobjid_1321020045629" style="width: 822px; height: 1151px; text-align: center; overflow: auto; background-color: rgb(142, 142, 142); position: absolute;" _widget="53"
if i change in the console the position to relative, the report returns in the right place..
Edited by: Emanuele Lanza on Nov 11, 2011 3:08 PM
Bug description and suggested workarounds have been posted in this thread:
It has been verified that the bug fix has been applied to Service Pack 3.