| commit | fc49e2802528eb948fabe705a8b5f695775ec01c | |
| author | Ross Lagerwall <rosslagerwall@gmail.com> | |
| Tue, 26 Mar 2013 08:16:58 +0000 (26 08:16 +0000) | ||
| committer | Uli Schlachter <psychon@znc.in> | |
| Tue, 26 Mar 2013 09:17:51 +0000 (26 10:17 +0100) | ||
| tree | 68a92844a63a88b691ba03d35667de264113f982 | treesnapshot (tar.gz zip) |
| parent | 8af54130d6f5b025999b5c209e96c2e8472270cf | commitdiff |
naughty: Don't interpret markup in titles
Since only the body text of a notification may contain markup,
by combining the two together and calling set_markup(), the
title would also get interpreted as if it had markup.
This could be seen with:
$ notify-send "Title & text" "<i>body text</i>"
The unescaped & would get interpreted as broken markup and so
naughty would fall back to escaping everything which would make
the "<i>" tags be shown rather than interpreted.
So, the title must always be escaped so that it is not interpreted
as markup.
Signed-off-by: Ross Lagerwall <rosslagerwall@gmail.com>
Signed-off-by: Uli Schlachter <psychon@znc.in>
Since only the body text of a notification may contain markup,
by combining the two together and calling set_markup(), the
title would also get interpreted as if it had markup.
This could be seen with:
$ notify-send "Title & text" "<i>body text</i>"
The unescaped & would get interpreted as broken markup and so
naughty would fall back to escaping everything which would make
the "<i>" tags be shown rather than interpreted.
So, the title must always be escaped so that it is not interpreted
as markup.
Signed-off-by: Ross Lagerwall <rosslagerwall@gmail.com>
Signed-off-by: Uli Schlachter <psychon@znc.in>
| lib/naughty.lua.in | diffblobblamehistory |