1.8 Not possible to activate form field on click

Bug #1483694 reported by Carla Berkers on 2015-08-11
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
High
Unassigned

Bug Description

In the original designs of the node details page, users could click on the deactivated fields to activate them and for instance change zone, cluster, mac address etc.

In the current build, a user has to click the edit button to make all the fields in a section editable.

I understand from Blake this functionality was removed just because we ran out of time and couldn't get it to really work well. However we can fix those issues and add that feature back in 1.9.

It would be important from a user experience perspective that the experience on the summary and power sections is similar to the storage and networking sections.

(For completion, Blake also said this: "If you just use contenteditable=true on general div's instead of using inputs, then its even easier. But that doesn't work on dropdowns. Thats more of an implementation detail.")

Tags: ui ux Edit Tag help
Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.9.0
Carla Berkers (carlaberkers) wrote :

Discussed with Blake, agreed that if we make all fields editable in the node networking and storage sections, we should do the same on the other sections to make it consistent.

Changes required:
- fields to show white background on hover
- fields to be editable on hover
- save new value when user clicks outside of field (when field loses focus)
- remove edit and save buttons on right hand side

Changed in maas:
assignee: nobody → Richard McCartney (ricgard)
Blake Rouse (blake-rouse) wrote :

I think we need to think on how we active the tags fields for all sections. Currently you press "edit" and then the ngTagsInput takes over to add the tagging. We need to figure out how this will work.

Richard McCartney (ricgard) wrote :

If this is the case we will need to change the input tags back to what it was originally. We can create a blank hover and focus style for all inputs and the tags.

Carla thoughts?

Changed in maas:
status: Triaged → In Progress
Richard McCartney (ricgard) wrote :

Also another thought what happens when there is no content the user is going to be looking at a screen where all the inputs are invisible, we will need placeholder text for all types of input / selects now.

Looking at this further I am seeing the disadvantages of hiding all the inputs on normal forms. Can we look at this a bit more next week and discuss it?

Rich

tags: removed: ux
tags: added: ux
Changed in maas:
assignee: Richard McCartney (ricgard) → nobody
status: In Progress → Triaged
Changed in maas:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers