When defining values for table cell types in EditTable definitions, it is unclear whether spaces around values are considered significant or not. For example, is the following definition
...|select, 1, a, b, c|...
the same as the following
or the following
...|select, 1, a , b , c |...
In other words, what is the value written into the table on each, if say, the firsts option was selected? Is it " a", "a", and " a "? Or "a", "a", and "a"? Or "a", "a", and "a "?
I have been testing a bit. It would have been better if the original reporter had been more specific on the problem. I think we all thought it was a doc issue. But there is more to it.
Try and edit the tables above with the Edit Table feature. Use IE. I did not try this in FF:
Try and change the first row to c c c c
And the next to d d d d
Note how the value of the last column changes to a in some rows. The way to work around it is to have no space before the comma and one space after. The plugin should not care about leading or trailing spaces when it comes to maintaining values.
As far as I can tell the plugin tries to cut leading and training spaces, which is also what I would have expected. But something goes wrong so it does not preserve the values. THAT is serious. Elevating to urgent.
- 03 Oct 2007
For select, radio and checkbox, the code now removes spaces before and after the values.
- 17 Oct 2007