Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341084

Summary: Behavior of Property Value cell editor after exceeding max characters is incorrect
Product: [Technology] Jubula Reporter: Zeb Ford-Reitz <zeb.ford-reitz>
Component: UIAssignee: Project Inbox <jubula.ui-inbox>
Status: CLOSED WONTFIX QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: major    
Priority: P3 CC: alexandra.schladebeck
Version: 0.9.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Zeb Ford-Reitz CLA 2011-03-28 07:08:46 EDT
While entering text into a Property Value cell editor, I went over the maximum number of characters allowed in this field (currently 255). A dialog appeared informing me of this, and the Parameter Value was applied. When I activated the cell editor again in order to resolve the issue, the character limit dialog appeared again. When I closed the dialog, the contents of the cell editor were cleared. I was provided with no opportunity to modify the existing text, which would then be completely gone unless I canceled the cell editor by pressing Escape or reverted the editor.

I would expect that the display of the character limit dialog does not deactivate my active cell editor, automatically applying my obviously unfinished changes. Instead, I would like the cell editor to be active after closing the dialog. I would expect the character that "caused" the dialog to not be entered.

In the same vein, I would expect that activation of the cell editor does not clear the editor. Perhaps it would be possible to present the contents as-is, allowing the user to resolve the issue before deactivating the editor in order to apply the changes. Barring that, perhaps the contents could be truncated to the maximum length.
Comment 1 Alexandra Schladebeck CLA 2014-01-08 08:32:54 EST
I agree with much of this, but I'm doing some spring cleaning. Since we've not got around to it thus far, and no one else has commented or added a ticket, it looks like it's not going to get done anytime in the near future. If anyone has other comments or reasons for fixing / prioritizing higher, please reopen.
Comment 2 Oliver Goetz CLA 2014-01-08 10:33:02 EST
Closed due to comment 1