- Issue created by @maskedjellybean
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
- First commit to issue fork.
- Merge request !11106Issue #3504118: Convert line breaks into HTML does not convert "\n" → (Open) created by annmarysruthy
- 🇺🇸United States smustgrave
Seems like something we should have test coverage for.
- 🇺🇸United States maskedjellybean Portland, OR
Wow, thank you @annmarysruthy! I didn't expect to have a fix so quickly. A patch from the MR fixed the issue! The test seems to make sense. Thanks again.
- 🇺🇸United States smustgrave
Not 100% sure about the solution. Not sure if there is a function that can called to do some of this and more but does address the issue. Will let committer decide if its good enough.
- 🇬🇧United Kingdom longwave UK
I'm not convinced this is the intent of the feature, when it says
\n
I think it means a literal line break (aka the newline character) and not the actual string\n
. - 🇬🇧United Kingdom longwave UK
Well, I'm not convinced this is a bug at all; the option is called
nl2br
because it callsnl2br()
on the output, and that presumably works as intended (although the additional test coverage here is nice, because currently we don't have any).Also not sure the test exercises the bug from reading it, running the test-only job to find out.
- 🇬🇧United Kingdom longwave UK
The test-only job passes without the fix, which means the test isn't demonstrating the problem described here.