Tickets without CSS

[janselato]

HI, i have problem with mails.
Mails created from freescout:

This message is difficult to read. Can you create new setting to fetch mails with original css?
Original message:

[ilyakonovalenko]

I think it is actually better to display text version by default. And HTML version as an option. HTML version is not safe, at least. It is also hard to read without original CSS styles which are removed. So if FreeScout developer decides to change it, my suggestion would be text version by default.

[janselato]

I know it's not safe, but this solution don't better.
I think, better add option in settings system to change default viewing tickets.

[ilyakonovalenko]

I know it's not safe, but this solution don't better.

Current HTML view is not looking good as well :-) Not sure if text view can be implemented via module hooks and filters, anyway it would be nice, simple and useful to have text view in core.

[freescout-helpdesk]

We'll leave this as help wanted. If someone can come up with some secure and reliable solution which would preserve original ticket's CSS please share and implement.

[janselato]

Implement CSP?
https://www.w3.org/TR/CSP2/#security-css-parsing

[janselato]

@freescout-helpdesk
Is it solution?
https://content-security-policy.com/style-src/

[ipruthi]

@freescout-helpdesk Is it solution? https://content-security-policy.com/style-src/

@janselato, I think the CSS feature asked on this thread has to do with inline CSS not being rendered by Freescout, not remote CSS files.

But thanks for style-src though, I didn't even know it existed!

[zigojacko]

I agree that I would prefer to be able to set default Text/HTML emails in the settings if anyone would like to take this on as a module or something...? 😂

[MarcoWel]

Copy/pasting + inserting pre-defined replies into the message textbox without formatting as default would already help a lot with mixed up styling in replies.

[freescout-helpdesk]

It looks like there is no a solution for this.

[jack-arturo]

I stumbled on this issue earlier today and solved it (for us). You can edit the allowed HTML and CSS in /config/purifier.php. After editing, run php artisan config:clear to clear the cache.

According to the guidelines this will be safe between updates: https://github.com/freescout-helpdesk/freescout/wiki/Development-Guide#development-guidelines