Rudder

the redmine interface seems to have done even worse. heh.
let me try again.

configSectionFoo

becomes
configSectionFoo

We had a similar report some time ago (ticket linked).

There is something to take into account: in some fields, we really expect as a user that the words will be trimed (ex: for a field waiting for a version in package management, for the name, etc).

It seems that a good behaviour would be to NOT TRIM text area (all example proposed are text area, and other examples we thing about where also only "long input").

So:

- we will try to remove trim in long input field kind (text area)
- and check that nothing break :)

Thanks for the report (and the reminder that this is an important topic)

François ARMAND wrote:

We had a similar report some time ago (ticket linked).

There is something to take into account: in some fields, we really expect as a user that the words will be trimed (ex: for a field waiting for a version in package management, for the name, etc).

It seems that a good behaviour would be to NOT TRIM text area (all example proposed are text area, and other examples we thing about where also only "long input").

So:

- we will try to remove trim in long input field kind (text area)
- and check that nothing break :)

There are some text (short) input fields that it would make sense not to trim to, like anywhere that matching a line in a file, unless a regex is able to entered. For instance in that same example I give above, the enforce file content, section header/footer fields need to allow leading spaces too, or they need to be able to accept a regex. thanks.