Xhtml: <nobr> tag in wrong place

The opening tag came before the IF statement,
and the closing tag was inside the IF statement.

This patch moves the opening tag inside the IF statement,
to match the closing tag.

html/Search/Elements/EditSearches | 2 ±
1 files changed, 1 insertions(+), 1 deletions(-)

(Patch is attached)

xhtml-extra-nobr-tag.patch (469 Bytes)

Remove a useless (and illegal) closing tag.

html/Search/Elements/SelectAndOr | 4 +±-
1 files changed, 2 insertions(+), 2 deletions(-)

(Patch is attached)

xhtml-weird-use-of-input.patch (679 Bytes)

RT is making XHTML that looks like this

That’s two “width” attributes, one of which is getting unnecessarily
HTML-encoded. This patch is a possible fix.

html/Elements/MyRT | 2 ±
1 files changed, 1 insertions(+), 1 deletions(-)

(Patch is attached)

xhtml-boxcontainer.patch (387 Bytes)

Thanks. Applied

Thanks. Applied

thanks, applied to 3.6, will merge into 3.7.On Nov 2, 2007 10:47 PM, Jason Long jlong@messiah.edu wrote:

The opening tag came before the IF statement,
and the closing tag was inside the IF statement.

This patch moves the opening tag inside the IF statement,
to match the closing tag.

html/Search/Elements/EditSearches | 2 ±
1 files changed, 1 insertions(+), 1 deletions(-)

(Patch is attached)


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:

If you sign up for a new RT support contract before December 31, we’ll take
up to 20 percent off the price. This sale won’t last long, so get in touch today.
Email us at sales@bestpractical.com or call us at +1 617 812 0745.

Best regards, Ruslan.