Project

General

Profile

Actions

Defect #13381

closed

Unclosed divs are interpreted in issue description and comments

Added by Denis Savitskiy about 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

<div class='inj' style="border: 5px red solid;">Hello, i'm a bug!

Actions #1

Updated by Denis Savitskiy about 11 years ago

  • Status changed from New to Resolved
Actions #2

Updated by Denis Savitskiy about 11 years ago

Thanks for fixing!

Actions #3

Updated by Jan Niggemann (redmine.org team member) about 11 years ago

  • Status changed from Resolved to Needs feedback
Actions #4

Updated by Jan Niggemann (redmine.org team member) about 11 years ago

Who fixed this? If someone fixed it at all?

Actions #5

Updated by Mischa The Evil about 11 years ago

Jan Niggemann wrote:

Who fixed this? If someone fixed it at all?

I think that Denis wanted to expose that "Unclosed divs are interpreted in issue description and comments" by using an issue description containing an unclosed div, as he did in this issue. However, the problem seems not to occur on rm.o (any longer?) thus he probably concluded that it has been fixed.

Denis, on what version of Redmine have you seen this behavior happen?

Actions #6

Updated by Denis Savitskiy about 11 years ago

Mischa The Evil wrote:

I think that Denis wanted to expose that "Unclosed divs are interpreted in issue description and comments" by using an issue description containing an unclosed div, as he did in this issue. However, the problem seems not to occur on rm.o (any longer?) thus he probably concluded that it has been fixed.

Exactly!

Denis, on what version of Redmine have you seen this behavior happen?

1.3.1.stable.4480

Actions #7

Updated by Mischa The Evil about 11 years ago

  • Affected version (unused) set to 1.3.1
  • Affected version set to 1.3.1

Denis Savitsky wrote:

Denis, on what version of Redmine have you seen this behavior happen?

1.3.1.stable.4480

This has certainly been an issue in past Redmine versions, IIRC. Though, I don't know/think if/that 1.3.x is supported any more. It's vulnerable for sure, when it is untouched.
Recap: my suggestion would be to upgrade to a newer, supported version of Redmine (and Rails stack).

Regarding this issue: should we close this one as won't fix? Should we care about the possible establishment of any precedent regarding (future) defect handling on rm.o, if yes...??

Actions #8

Updated by Denis Savitskiy about 11 years ago

Mischa The Evil wrote:

Regarding this issue: should we close this one as won't fix? Should we care about the possible establishment of any precedent regarding (future) defect handling on rm.o, if yes...??

Sure, close it! We are currently upgrading to Redmine 2.2.3. I'll add bugs if they are found. We use Redmine constantly for 3 years.

Actions #9

Updated by Toshi MARUYAMA about 11 years ago

  • Status changed from Needs feedback to Closed

Thank you for your feedback.

Actions

Also available in: Atom PDF