View Issue Details

IDProjectCategoryView StatusLast Update
0020503mantisbtbugtrackerpublic2018-08-15 01:54
ReportercproensaAssigned To 
PrioritylowSeverityminorReproducibilityN/A
Status newResolutionopen 
Product Version1.3.0-rc.1 
Target VersionFixed in Version 
Summary0020503: Consider not expanding issues and notes internal links in some places
Description

When using the # character with a number, it automatically (if the number is an existing bug_id) expand to an url that point tho that issue number (also for comments)

While it's a useful feature, there are some places where they probably should not be expanded, for a better presentation.

For example:
Summary text. its often an unintended use of the character #.
History lines. As part for a changed field, the purpose is clearer if shown as unprocessed text.
Print page: As a document targeted for printing, does it need hyperlinked text?

TagsNo tags attached.

Relationships

related to 0011763 new Ability to escape bug linking 

Activities

vboctor

vboctor

2016-01-15 04:24

manager   ~0052317

For the summary field, I don't think there is a reason to assume that such bug links are not valid. For the email representation, I think the HTML emails will make it look natural.

There will be cases where there is a body of an issue that has an error code number with the # prefix. This is likely to happen in the description or additional info, etc. The only case is to change the bug number prefix. Even escaping doesn't necessarily work, if these bugs are auto-logged or are a copy and paste of a big error message.

Note sure about the cases for history that you have in mind.

cproensa

cproensa

2016-01-15 05:32

developer   ~0052319

Note sure about the cases for history that you have in mind

it came by looking at this issue history: 0020479
changing the subject, due to a non-desired # substitution, is showing the incorrect link in history

cproensa

cproensa

2016-01-15 05:41

developer   ~0052320

For the summary field, I don't think there is a reason to assume that such bug links are not valid. For the email representation, I think the HTML emails will make it look natural.

Let's see this way: I'm not saying that using URL in the summary text is invalid.
It's the place where the summary text is used what can make using urls acceptable or not.

For example:
Summary text in bug view: may be ok, natural as you stated.
Summary text in history: probably bad
Summary text for bug print: not needed (#nnnn is clearer anyways)
summary text in an email subject: i dont think an url would be even allowed there

So, my thinking may lead to needing an additional "context" to use with the formatting plugin, which should be specified by the caller. And based of that context, parametrize whether translate urls or not.

jes

jes

2018-08-15 01:54

reporter   ~0060433

Last edited: 2018-08-15 01:54

View 2 revisions

The same problem occurs on the bug view page with an email address as summary. This produces invalid HTML code:
<span>view.php?id=1234</span>
It was a little bit weird to click on an issue link and see the email client coming in front.

Issue History

Date Modified Username Field Change
2016-01-11 18:48 cproensa New Issue
2016-01-12 01:52 atrol Relationship added related to 0011763
2016-01-15 04:24 vboctor Note Added: 0052317
2016-01-15 05:32 cproensa Note Added: 0052319
2016-01-15 05:41 cproensa Note Added: 0052320
2018-08-15 01:54 jes Note Added: 0060433
2018-08-15 01:54 jes Note Edited: 0060433 View Revisions