ImproveRichTextHandling - Revision history

Admin: 7 revisions imported

2016-04-06T20:11:24Z

7 revisions imported

New page

I have several issues with the rich text handling of RT 3.8.8. A rich text email looks a lot different in the Display page from the Update page. For example, color text is only shown when updating a ticket. Part of the reason is because the HTML scrubber for the Display view uses different scrubbing rules from when the content of a transaction is quoted for Update view. Unclosed tags can mess up an entire ticket in the Display view, but then these tags are closed when they are quoted and sent to Update. This article is dedicated to improving rich text handling in RT.

<u>(Please note - allowing tables through in HTML emails allows you to do malicious things to RT's ticket history display. Similarly, unilaterally allowing styles opens you up to attacks.)</u>

ScrubHTML:
$ diff /usr/share/request-tracker3.8/html/Elements/ScrubHTML html/Elements/ScrubHTML
63a64,66
> color => 1,
> type => 1,
> align => 1,
68c71
< qw[A B U P BR I HR BR SMALL EM FONT SPAN STRONG SUB SUP STRIKE H1 H2 H3 H4 H5 H6 DIV UL OL LI DL DT DD PRE]
---
> qw[A B U P BR I HR BR SMALL EM FONT SPAN STRONG SUB SUP STRIKE H1 H2 H3 H4 H5 H6 DIV UL OL LI DL DT DD PRE BLOCKQUOTE TABLE TBODY TR TH TD]

(more to come later)

75.147.59.54 at 16:13, 21 December 2010

2010-12-21T16:13:23Z

← Older revision		Revision as of 12:13, 21 December 2010
Line 1:		Line 1:
	I have several issues with the rich text handling of RT 3.8.8. A rich text email looks a lot different in the Display page from the Update page. For example, color text is only shown when updating a ticket. Part of the reason is because the HTML scrubber for the Display view uses different scrubbing rules from when the content of a transaction is quoted for Update view. Unclosed tags can mess up an entire ticket in the Display view, but then these tags are closed when they are quoted and sent to Update. This article is dedicated to improving rich text handling in RT.		I have several issues with the rich text handling of RT 3.8.8. A rich text email looks a lot different in the Display page from the Update page. For example, color text is only shown when updating a ticket. Part of the reason is because the HTML scrubber for the Display view uses different scrubbing rules from when the content of a transaction is quoted for Update view. Unclosed tags can mess up an entire ticket in the Display view, but then these tags are closed when they are quoted and sent to Update. This article is dedicated to improving rich text handling in RT.

			<u>(Please note - allowing tables through in HTML emails allows you to do malicious things to RT's ticket history display. Similarly, unilaterally allowing styles opens you up to attacks.)</u>

	ScrubHTML:		ScrubHTML:

173.10.126.249 at 23:06, 20 December 2010

2010-12-20T23:06:32Z

New page

I have several issues with the rich text handling of RT 3.8.8. A rich text email looks a lot different in the Display page from the Update page. For example, color text is only shown when updating a ticket. Part of the reason is because the HTML scrubber for the Display view uses different scrubbing rules from when the content of a transaction is quoted for Update view. Unclosed tags can mess up an entire ticket in the Display view, but then these tags are closed when they are quoted and sent to Update. This article is dedicated to improving rich text handling in RT.

ScrubHTML:
$ diff /usr/share/request-tracker3.8/html/Elements/ScrubHTML html/Elements/ScrubHTML
62,63c62,67
< style => qr{^(?:(?:color:\s*rgb$\d+,\s*\d+,\s*\d+$)|
< (?:text-align:\s*))}ix,
---
> # style => qr{^(?:(?:color:\s*rgb$\d+,\s*\d+,\s*\d+$)|
> # (?:text-align:\s*))}ix,
> style => 1,
> color => 1,
> type => 1,
> align => 1,
68c72
< qw[A B U P BR I HR BR SMALL EM FONT SPAN STRONG SUB SUP STRIKE H1 H2 H3 H4 H5 H6 DIV UL OL LI DL DT DD PRE]
---
> qw[A B U P BR I HR BR SMALL EM FONT SPAN STRONG SUB SUP STRIKE H1 H2 H3 H4 H5 H6 DIV UL OL LI DL DT DD PRE BLOCKQUOTE TABLE TBODY TR TH TD]

(more to come later)