Unanswered

Html styling not working since 21/05/2024

(0) Share

Report

Posted on by michaelbratley

I have multiple flows that create styled html files and then convert these to pdf. Since today, 21/05/2024, the styling has stopped working across all flows I have created, even though they have not been changed or edited. Has anyone else experienced this issue?

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (0)

Sort by

michaelbratley on at

Like
a
(0)

Report
Copy link

Link copied!

I'm assuming that some validation has changed on Microsoft's end. After checking the html there were some unrecognised characters in the string and this appeared to be causing the issue. After removing these characters the formatting returned as expected.

Was this reply helpful? Yes No
Jprado1 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, i'm having the same issue, all my pdf worked great until the 21, now all of my html to pdf convertions are not styled correctly, how exactly did you check which characters were unrecognized? I'll appreciate your help, thanks!

Was this reply helpful? Yes No
michaelbratley on at

Like
a
(1)

Report
Copy link

Link copied!

I used this html validator to find the characters - https://jsonformatter.org/html-validator

Was this reply helpful? Yes No
wanderingartist 8 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi, we're having the same issue on the same timeline here. It would be nice if Microsoft would tell us these kinds of breaking updates are coming rather than letting us find out the hard way.

Was this reply helpful? Yes No
srastogi 21 on at

Like
a
(0)

Report
Copy link

Link copied!

I have many flows that send emails with css code formatting. AFAIK, HTML code in the email body is fine and also works correctly when testing it on HTML validator like: W3Schools Tryit Editor

Problem for me seems to have occurred from 25 June 2024 onwards when Windows did a big update. Any updated computers are not showing email with HTML correctly (like how your example above is).

Wonder if this is a big enough problem for Microsoft to notice and rectify?

Was this reply helpful? Yes No
wanderingartist 8 on at

Like
a
(1)

Report
Copy link

Link copied!

We ended up reworking the formatting of our HTML-to-PDF export. We were using the former default charset=windows-1252 (as seen in the screenshot):

We updated it to UTF-8 and tightened up the HTML formatting and made a few other adjustments. The output looks right again! Took me and a developer a few hours to get it sorted out once we identified the charset as the most likely culprit.
So it seems like Microsoft enforced some updated standards for HTML encoding in the Power Apps ecosystem. This probably affects people who've used Word or Outlook to create rich text to begin with.

Ironically, Microsoft's HTML code, when created from these apps, is horrific and poorly formatted. Best practice is to cleanse it of spans and in-line formatting first, apply CSS, and then use that HTML in your template. Or just write it with Copilot.

Was this reply helpful? Yes No
srastogi 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Update - It seems like Microsoft has updated Outlook and the formatting is showing correctly for HTML in the email body including tables and colors and other css.

Was this reply helpful? Yes No