more readable "closed" style

[Christian Boos]

The current strikethrough style is barely readable, as already mentioned in the past, like in #9981. If people can get used to it for numbers (but what about #8080 for example?), it's really a bother for milestones (a milestone that didn't turn into a release) or comments (as was said before).

We just revived the subject in #10012 (see comment:42), with several new interesting proposals, notably the one from Peter which is to append an unicode 'CHECK MARK' character to the ticket (✓).

[anonymous]

What will be the syntax to checkmark a milestone?

[Remy Blank]

[11152] removes the closed CSS class from the ticket ID, to avoid the strike-through style. Once we have a better style for links to closed tickets, we can try re-adding the class.

[Christian Boos]

Stumbled upon ​http://trac.sagemath.org/sage_trac/ticket/7549, interesting. They didn't remove the strike-through but use a color code for the status.

[lkraav <leho@…>]

I am always down with color coding, one of the most intuitive ways to implement things

[theultramage@…]

I observed that links with custom title text also get strikethrough. For me, the open/closed property has less importance than the text that the author of the link wants me to read. So until a better mechanism is found, I suggest that only links in their 'raw' form get the strikethrough processing. Or, in a messy alternative way, special syntax to define if you want strikethrough or not.

[Ryan J Ollos <ryan.j.ollos@…>]

Replying to theultramage@…:

… So until a better mechanism is found, I suggest that only links in their 'raw' form get the strikethrough processing.

There was agreement that this was a defect, and the patch in #10742 fixes the issue.

[Ryan J Ollos]

Retargetting tickets to narrow focus for milestone:1.2. Please move the ticket back to milestone:next-dev-1.1.x if you intend to resolve it by milestone:1.2.