Closed reederz closed 6 years ago
Dan, can you see if you can reproduce this when you have a moment? No rush. It could be that it's specific to Lars' environment (I saw the behaviour on his laptop myself).
I don't have the option to update yet, will try when it pops up
@danmindru I was poking around today and found this https://www.youtube.com/watch?v=x-pATsvrQQc . Then I realised that those instructions can be adapted to our signatures too. Here's roughly how it goes:
This worked perfectly for Lars. Let me know if you see any problems with this approach.
If this approach is fine with you, you or I could easily setup a CI workflow to automatically publish signatures as webpages E.g. on github pages or one of our servers.
yeah it's an alternative way, BUT the responsive styles (<style>
block in <head>
) are going to be lost during the process.
That's why we went through all the trouble before. When editing the source directly we could be sure everything in <head>
makes it in the signature.
Bugger... Well, it will do for now as it's better than nothing.
For what it's worth, responsiveness works on:
Can't test outlook though. Is that where it might not work, you think?
I'd test it on a mobile device. The email content should fit whatever size the mobile device viewport is (both portrait and landscape) without having to scroll horizontally.
Check your gmail or @fadeit.dk email when you have time - I've sent you a test.
Even though the current OS X setup instructions are super sketchy, they do work. Or at least they used to. Meet High Sierra - the nightmare of responsive html signatures.
Jokes aside, editing signature on disk with email client closed does fuck all because once you open the client, the signature gets overwritten. Could it be related to the new filesystem they launched?
CC: @danmindru