-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for monospace on plain-text body #462
Comments
I did this on purpose because most modern mail clients display plain text mail as regular text without fixed width fonts. Gmail, for instance. You can often configure clients to display fixed width fonts, but it's a departure from typical configuration. |
Can we at least have white-space: pre-wrap; then ? |
After a bit of poking around this does seem like a good idea. Fixed in e6f8397. |
To try it out in the latest beta:
Edit: Also now shipped in v0.8.0, so you can also upgrade with:
|
docker-compose
Pulling mail (sj26/mailcatcher:)... cli: mailcatcher --version |
Whoops, I forgot to bump latest, sorry! Try it again. |
Tested (v.0.8.1), it's not working
|
Weird! I can't replicate this. It's working fine on Safari, Firefox and Chrome for me when using latest MailCatcher v0.8.1. I get an inspector like this: Can you provide a reproduction case? Or more details? That "src" starting with a slash "/" makes me think you might not be running the latest version? Relative paths were introduced in 0.8. |
Yes, it's working, css coming thru (probably container was hanging in there). All in all, without the monospace font still not optimal for me, |
Great! I do appreciate that some folks may prefer monospace, but that's not a default in most contemporary mail clients, and so I don't think it shoud be a default here. It'd be nice to have a button for switching to monospace and back eventually, but that's likely to happen after a redo of the whole frontend (#473). |
Thank you for a great tool to catch mail in development.
Would it be possible to set a formatting CSS style on the element of the plaintext?
The text was updated successfully, but these errors were encountered: