-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support for HTML special character notations in message list/header display #3812
Comments
Comment by hh on 9 Jun 2012 01:26 UTC === TO REPRODUCE ===
As of 0.8-rc, this will be shown as:
|
Comment by hh on 10 Jun 2012 12:12 UTC === SUPPLEMENTAL ===
Note: |
Comment by @alecpl on 3 Aug 2012 08:07 UTC I think this is a bug that HTML entities in subject/headers are not "sanitized". |
Milestone changed by @alecpl on 3 Aug 2012 08:07 UTC later => 0.8-stable |
Comment by @thomascube on 5 Aug 2012 11:19 UTC I guess our duplicate quotation check (in rep_specialchars_output()) is causing this issue. We should remove that and test whether there are situations where indeed HTML characters are quoted twice. |
Comment by @alecpl on 15 Aug 2012 14:34 UTC I've commented it and we have few issues now (mail subject in on reply, contact form inputs). Maybe this is one form-elements related issue. Need more testing. |
Comment by @alecpl on 17 Sep 2012 13:10 UTC I commited two changes to a new branch 'html_ent'. Works for me, but I'd like to test this change with some plugins. |
Comment by @alecpl on 21 Sep 2012 08:15 UTC Merged. |
Status changed by @alecpl on 21 Sep 2012 08:15 UTC new => closed |
Reported by hh on 8 Jun 2012 13:37 UTC as Trac ticket #1488523
It would be nice to have HTML special character notations shown verbatim in the Subject field of email. As of 0.8-rc, such notations, typically
&
and©
, are directly rendered by the browser. If you have©
in the Subject field, for example, it appears as a copyright symbol () in the message list and header panes.Note: With my setup,
Q()
instrict
mode doesn't seem to work for this purpose, and I had no luck extending the underlyingrep_specialchars_out()
function - I'm now experimenting with something like:The following changes are against a7d5e3e:
Keywords: header subject literal
Migrated-From: http://trac.roundcube.net/ticket/1488523
The text was updated successfully, but these errors were encountered: