Lock icon statues in Main Window

[wpx12011]

When first navigate to a record in the Main Window, the Contact Detail section will show an open lock with all contact details.

Click the icon once will hide all details but still show an open lock

Click it once more it will show details again with a locked icon. This is confusing, should change the default status of the icon to locked.

[nus-pe-script]

Team's Response

The intuition of the lock icon should make sense as it implies the action of the button, not the current state.

This is similar to the iPhone lock screen and mute icon:

Example:

The icon Lock Rotation does not mean your phone is currently locked, the icon rather represents the action you want to do. So click on the Lock Rotation icon will lock your screen (i.e. you cannot rotate your screen).
.

After clicking on the Lock Rotation button, it will change to Unlock Rotation icon.

However, your phone screen rotation is actually currently "locked" - the Unlock Rotation represents the "next" action you may want to do to change your phone to "unlocked" rotation, not the current state of your screen rotation.

We decided to use the same logic for our app as we feel that this is quite intuitive - it has been proven by the common use in Apple devices.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: The team is not answering to my issue raised. I am not talking about the logic between action and icon, but I'm suggesting that there is a display bug in the icon.

In my original issue description, I showed 3 screenshots which depicts 3 actions:

1. When the app is first open, the default display shows contact detail and an open lock.
2. When I click the lock icon once, the display hides contact details, but still showing an open lock.
3. When I click the lock icon once more, the display shows contact details and a locked lock.

The team is trying to explain that the lock icon is behaving correctly in steps 2 and 3 (which I agree), but my actual issue is about the display bug in step 1. Therefore, I do not agree with the team's rejection.

---

❓ Issue type

Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]

• I disagree

Reason for disagreement: Please refer to my reasoning in response to reclassification of severity, I think this issue is a functionality bug since it's an incorrect behavior.

---