clicking app's home button does not clear fields

Description

Description

Clicking the "Check out" icon in the navigation button does not reset the app to its default state

Expected results

The app would reset to its default state, i.e. all fields should be cleared.

Actual results

Nothin'.

Steps to reproduce

  • Click the Checkout app icon in the main nav

  • Type something into a field. Any field.

  • Click the Checkout app icon in the main nav. All fields should be cleared but they aren't.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1
  • 21 Mar 2019, 07:02 PM

Checklist

hide

TestRail: Results

Activity

Show:

Cate BoeremaJuly 3, 2019 at 9:56 AM

Per Filip's latest comment, closing as wont do

Filip JakobsenMarch 21, 2019 at 7:04 PM

Hi Cate,

Sorry for the late reply on this. This behavior will be moot with the Current App Context Menu pattern if Check Out has any preferences, settings or help pages (although a similar question may then arise for the "home" option in the Current App Context Menu. Perhaps this should be replaced by a "Clear all fields" or "End session" option).

Generally, clicking the home button in apps should not clear the input fields on the home screen (e.g. if people have performed a search in users, codex search or elsewhere). To make sure the behavior is consistent in the full system, this should not happen in Check Out either.

It feel that it should be made clearer how to clear all the fields in the Check Out app if people attempt to use the app icon for this purpose. In the original design (see attached, or https://ux.folio.org/prototype/en/check-out?view=full and choose UX iteration 2 under the screen), the current "end session" button was signifcantly more prominent in size and positioning, and the wording was different. Some of those things could perhaps be done in the current design to make it clearer how to clear the fields.

In any case, it should be avoided that all fields are cleared when clicking the home screen.

Let me know if you have any other questions. Thanks!

Cate BoeremaMarch 21, 2019 at 5:25 PM

it looks like the expected behaviour on this needs clarification and hasn't responded.

Oleksiy_LemeshkoFebruary 15, 2019 at 3:40 PM

we faced some issues trying to define the right behaviour.
Filip, can you please advise what the behaviour should be in this case?

Cate BoeremaOctober 26, 2018 at 10:01 AM

Okidoke. Thanks!

Won't Do

Details

Assignee

Reporter

Priority

Development Team

Prokopovych

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 8, 2018 at 10:11 AM
Updated July 3, 2019 at 9:56 AM
Resolved July 3, 2019 at 9:56 AM
TestRail: Cases
TestRail: Runs

Flag notifications