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
Change header separator color to Outlook default #108
Comments
@cnmicha When initially developed the RWH add-on that time I took a color code from Outlook. I think the Outlook client still uses that color. I can see with my macOS Outlook client v16.52 (21080801). May I know where do you see a black color? web version? |
Looks like Outlook has different default styles in Windows vs Mac. While css is used in email sent by O365 Outlook, I simplified styling into html tags without css and ended up with below html snippet. I had 24 hour clock but otherwise regular US English settings. Note how separator line is produced by O365 Outlook client in Windows, with line color E1E1E1. Below snippet is 100% similar than how replying or forwarding with O365 Outlook client in Windows.
|
@anttiisoaho Thanks for providing the HTML string; it is helpful for understanding. @cnmicha @anttiisoaho I will change the header line default color to |
@jeevatkm just note the corrrect color value:
|
@anttiisoaho Thanks. I will take care of it. |
@cnmicha @anttiisoaho I'm working on the WebExtension version of RWH. The branch is here. I require a sample string of the following in multiple languages for a Reply
Forward
|
Plain text example from O365 (US English) if this is what you wanted - there is no difference in reply or forward so this applies to both:
|
Thanks, @anttiisoaho, for your help. |
Hi,
how do you think about changing the default value of the preference
extensions.replywithheader.header.separator.line.color
to#1E1E1E
which is the header separator line color of Outlook?What was the idea behind choosing the current default color (
#B5C4DF
)?If you like, I can provide a pull request for this.
Thanks!
The text was updated successfully, but these errors were encountered: