Posted 5 September 2023, 7:55 am EST - Updated 5 September 2023, 8:00 am EST
We just recent update to v17 and addressed all the GDI references changes or so we hope we did. This past release, we enforced all code-behind section reports to use CompatabilityMode = CrossPlatform. This was met with good success for clients with Windows. Unfortunately anyone using our web application on Mac with Safari or Chrome would see ‘font glyphs’ instead of characters.
Please see attached.
With some long troubleshooting, we resorted to forcing all reports back onto GDI for continued support. Thru our investigation, we found that only controls/components with a style attribute of a particular set would render incorrectly. Any component with ‘font-style’, ‘font-weight’, ‘text-decoration’ was the majority of our culprits.
What would you recommend our next source of action be for becoming Cross Platform compatible?
More about our setup
Deployed to Azure VM (windows instance)
User initiates report request from web app
Server collects and generates section report (code-behind), and returns a .rdf
we create a new iframe that take the rdf and generates a pdf (Section.Pdf.PdfExport)
finally we embed the generated .pdf into the browser for end user to review.
