This task is about learning from volunteers whether there are cases where the ===Proposed requirement below could be problematic.
We need to do our best to understand what these potentially problematic cases are so we can evaluate if and how the ===Propose requirement should be implemented.
- What we are trying to learn
- In what, if any, scenarios the === Proposed requirement would cause people issues.
- The change that is being considered. See ===Proposed requirement below.
- The reasons this change is being considered.
- Usually, line breaks in signatures will cause the markup to break when the signature is used in a nested comment (in a list item)
- When the line break is inside a link label, it does not break the markup, but it can cause dirty diffs in Parsoid (T265094) and can be confusing to people reading the wikitext and trying to reply:
- en.wikipedia.org: user adding a signature with a line break – a later edit has a dirty diff because of it
- simple.wikipedia.org: user adding a signature with a line break – a later edit has a dirty diff because of it
- ar.wikipedia.org: user adding a signature with a line break – a later edit has a dirty diff because of it
Disallow line breaks in signature
The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment, and can cause issues with tools used on discussion pages.
Adding line breaks has already been impossible, unless you used a substituted template for your signature or edited your preferences programatically. This just closes that loophole.
- The ===Post contents are published in place(s) where people who have a stake in this work are likely to see it.