[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556412#action_12556412
 ] 

Stefan Seelmann commented on DIRSTUDIO-242:
-------------------------------------------

This is the intended behaviour ;-)

I remember one use case: When adding an attribute or value, the default 
ValueEditor is opened. If the user wants to edit it using another value editor, 
s/he must escape editing and select another value editor from the context menu. 
When we remove the empty value after escape this won't be possible.

Do you think, this is a valid use case? 

BTW: The empty value is marked (bold and red colored by default) to signal that 
this value isn't written to the directory.

> Inconsistent state of the Entry Editor after using "New Value" (or "New 
> Attribute...") and pressing "Escape".
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-242
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-242
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 1.0.1
>            Reporter: Pierre-Arnaud Marcelot
>             Fix For: 1.1.0
>
>
> Inconsistent state of the Entry Editor after using "New Value" (or "New 
> Attribute...") and pressing "Escape".
> Steps to reproduce:
> - Display an Entry in the Entry Editor.
> - Click on the "New Value" button
> - Press "Escape"
> => The Entry Editor is left with an empty value for the attribute and does 
> not reflect the actual state on the server.
> I think the newly added value should be removed.
> The same problem occurs with the "New Attribute..." button.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to