Liaison statement bodies are conditionally reformatted and they shouldn't be. #10129
Description
Description
At the moment, liaison statement bodies are shown on the liaison detail page after pushing them through a filter that looks to see if any lines are longer than 80 characters and, if so, reflowing the text to break them at that limit.
This is problematic for several reasons:
- It surprises liaison managers/coordinators when what's rendered does not match what they thought they entered, if they just happened to cross that 80 character limit somewhere
- It makes changing the view more difficult than it needs to be - any change to this conditional processing will affect existing liaison statements differently.
The application needs to make a choice about whether the liaison body is expected to be rendered as provided, or if it is expected to be reformatted, and if reformatting/reflowing is allowed, there should be well understood expectations for its effect. Two possible pays forward are
- Don't reflow/reformat at all. Always show the body as is.
- Shift the body to allow markdown formatting, make it clear that's what's used, and show a preview while editing.
Either will require an effort to adjust existing bodies to display correctly after the change.
Code of Conduct
- I agree to follow the IETF's Code of Conduct