Altinn / app-frontend-react

Altinn application React frontend
BSD 3-Clause "New" or "Revised" License
18 stars 31 forks source link

Better design and guidelines for presenting dynamic data for the end-user #207

Open Febakke opened 3 years ago

Febakke commented 3 years ago

Description

This is a draft of an issue that should look into if we need to expand functionality for presenting data. Today we have supported using read-only fields to show for example the user pre-fill data taken from some source, the sum of an calculation based on input by the user and generally show the user a dynamic value based on some source that the user can not edit. One challenge with this solution is that a read-only will get keyboard focus and if you choose to make it disabled you get another bunch of potensial UU problems. The best way to do this is to present this data as simple texts. Input fields should be used for user input and not present the user with information.

Design Tasks

Screenshots

Screenshots or links to Figma (make sure your sketch is public)

Considerations

Describe input (beyond tasks) on how the user story should be solved can be put here.

Ops requirements

Are there any requirements for monitoring? What is being built and what could go wrong? Are there any requirements related to backup?

Acceptance criteria

Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)

Specification tasks

Development tasks

Add tasks here

Test

Add test cases here as checkboxes that are being tested as part of the changes.

Definition of done

Verify that this issue meets DoD (Only for project members) before closing.

olemartinorg commented 2 years ago

Ever so slightly related to:

FinnurO commented 1 year ago

Slightly relevant for #744