Apache OpenOffice (AOO) Bugzilla – Issue 88072
Data validity "list" will be changed to "cell range" if input a long string as a list item
Last modified: 2022-12-05 17:56:36 UTC
The defect PD steps: 1. Open file menu: data->validity, and popup the validity dialog; 2. Select allow "List" in the combbox, and input several items in the "Entries", e.g. item1,item2,1234567812345678123456781234567812345678123456781234567812345678123 4567812345678123456781234567812345678123456781234567812345678123456781234567812 3456781234567812345678123456781234567812345678123456781234567812345678123456781 2345678123456781234567812345678. The third item length is more than 254. 3. Click "OK" button to close the dialog; 4. Cursor in the cell and reopen the validity dialog; 5. Now the dialog is changed to allow "cell range" in the combbox, and the source is changed to "item1","item2" and "34567812345678123456781234567812345678123456781234567812345678123456781234 5678123456781234567812345678123456781234567812345678123456781234567812345678123 4567812345678123456781234567812345678123456781234567812345678123456781234567812 3456781234567812345678". The beginning 2 characters "12" of the third item is cut, and the length is changed to 254.
Checked in OOo300_m3_EN on WinXP. The reproducible steps is same, but the result differs. Follow your steps, I find the third item is “123456781234567812345678123456781234567812345678123456781234567812345678123456 7812345678123456781234567812345678123456781234567812345678123456781234567812345 6781234567812345678123456781234567812345678123456781234567812345678123456781234 567812345678123456 (pay attention to the double quotation marks) but not 1234567812345678123456781234567812345678123456781234567812345678123 4567812345678123456781234567812345678123456781234567812345678123456781234567812 3456781234567812345678123456781234567812345678123456781234567812345678123456781 2345678123456781234567812345678.
The string exceeding 254 characters gets truncated and a double quotation mark is added (though there is a slight difference in behaviour between version 2.4.0 and, for example, version 3.1.0). Anyway, as of version 3.1.1 the issue does not occur (NOT REPRODUCIBLE).
Closing due to comment #2