Skip to content

Handle hidden field state by hiding reason and distinguish revealed questions #520

Description

@prestoncabe

Desired behavior

Hidden fields should be treated differently depending on why they are hidden:

  • Hidden by a user-defined rule on the field: consider the field unanswered/null. (I believe this is the default in form-js)
  • Hidden because all associated benefits have been determined: preserve the state the field had before it was hidden, whether answered, unanswered, or another state.

When the user toggles “show questions that were hidden”, questions that would otherwise be hidden should be visually differentiated from questions that are still in play. Possible treatments include muted/greyed styling, italics, or a visible tag; the specific treatment is open for design discussion.

Acceptance criteria

  • Rule-hidden fields are considered unanswered/null.
  • Fields hidden because all associated benefits have been determined retain their prior state.
  • Revealing otherwise-hidden questions clearly distinguishes them from questions still in play.

Related: #503

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions