Change Details

**Motivation** As a user I want to be able to edit existing data entries of the termbox. This will increase data quality and the multilinguality of Wikidata. **Workflow** **Given I'm ** on a page showing the termbox component in an editable state, **when** clicking the edit button (pen icon) **then** the termbox entries (labels, descriptions and alias(es)) of all shown languages will switch to edit mode. **Acceptance Criteria** [x] There is an edit button on the top of the page (next to the label of the interface language) [] When the user clicks on the edit button [x] all entries become editable, with label, description and alias texts turning into input fields !! Only labels and descriptions!! [] The editing fields are correctly styled (see: T218572) [] The input filed has the text heights plus 8px padding to each side [] it is depicte by a 1px inside border in Base50 [] it has 2px radiuses [] between text fields we have 8px padding [] the input field allows line breaks and adjusts in heights according to that [] the input field spans over the defined width of the "content" column [] existing content of the fields is shown fully. A follow up story will extend this to do text wrapping if needed. [] if fingerprints are uncollapsed, they are immediately in edit mode, too [] The edit button turns into a save button [] When the user clicks on the save button, all entries are saved in their current state. We operate under the assumption that all entity information is in valid wikidata content languages only. [] The save icon disappears and the edit icon will be shown again [] The page is back in reading mode [] The edit and save buttons follow the following design specifications: (BUT if this is unexpectantly not easy or timeconsuming, please stop) [] colors: default: #3366cc, hover: #447ff5 (not relevant for touch, but for people using mobile on desktop), active (upon clicking the button for 0,5 s): #2a4b8d [] If other changes had been made since the users started editing, the new info is reflected when the saved object is shown, without any extra notice to the user [] The new editing behavior does not interfere with general edit conflict detection **Mocks** [[ https://www.figma.com/file/g86G4bYOcUoIPwEbN041nq/180607_Termbox-Mobile-Sprint?node-id=724%3A425 | Figma file ]] containing all the design specifications / mocks {F28203334} {F28203336} {F28203341} {F28203345} {F28203344} **Notes** * This story does not contain cancel mode, and does not catch errors * Placeholders are covered in T217000

**Motivation** As a user I want to be able to edit existing data entries of the termbox. This will increase data quality and the multilinguality of Wikidata. **Workflow** **Given I'm ** on a page showing the termbox component in an editable state, **when** clicking the edit button (pen icon) **then** the termbox entries (labels, descriptions and alias(es)) of all shown languages will switch to edit mode. **Acceptance Criteria** [x] There is an edit button on the top of the page (next to the label of the interface language) [] When the user clicks on the edit button [x] all entries become editable, with label, description and alias texts turning into input fields !! Only labels and descriptions!! [] The editing fields are correctly styled (see: T218572) [] The input filed has the text heights plus 8px padding to each side [] it is depicted by a 1px inside border in Base50. The 1px is taken off from the 8px padding described above so that we remain in a grid dividable by 8/4px [] it has 2px radiuses [] between text fields we have 8px padding [] the input field allows line breaks and adjusts in heights according to that [] the input field spans over the defined width of the "content" column [] existing content of the fields is shown fully. A follow up story will extend this to do text wrapping if needed. [] if fingerprints are uncollapsed, they are immediately in edit mode, too [] The edit button turns into a save button [] When the user clicks on the save button, all entries are saved in their current state. We operate under the assumption that all entity information is in valid wikidata content languages only. [] The save icon disappears and the edit icon will be shown again [] The page is back in reading mode [] The edit and save buttons follow the following design specifications: (BUT if this is unexpectantly not easy or timeconsuming, please stop) [] colors: default: #3366cc, hover: #447ff5 (not relevant for touch, but for people using mobile on desktop), active (upon clicking the button for 0,5 s): #2a4b8d [] If other changes had been made since the users started editing, the new info is reflected when the saved object is shown, without any extra notice to the user [] The new editing behavior does not interfere with general edit conflict detection **Mocks** [[ https://www.figma.com/file/g86G4bYOcUoIPwEbN041nq/180607_Termbox-Mobile-Sprint?node-id=724%3A425 | Figma file ]] containing all the design specifications / mocks {F28203334} {F28203336} {F28203341} {F28203345} {F28203344} **Notes** * This story does not contain cancel mode, and does not catch errors * Placeholders are covered in T217000

**Motivation** As a user I want to be able to edit existing data entries of the termbox. This will increase data quality and the multilinguality of Wikidata. **Workflow** **Given I'm ** on a page showing the termbox component in an editable state, **when** clicking the edit button (pen icon) **then** the termbox entries (labels, descriptions and alias(es)) of all shown languages will switch to edit mode. **Acceptance Criteria** [x] There is an edit button on the top of the page (next to the label of the interface language) [] When the user clicks on the edit button [x] all entries become editable, with label, description and alias texts turning into input fields !! Only labels and descriptions!! [] The editing fields are correctly styled (see: T218572) [] The input filed has the text heights plus 8px padding to each side [] it is depicted by a 1px inside border in Base50. The 1px is taken off from the 8px padding described above so that we remain in a grid dividable by 8/4px [] it has 2px radiuses [] between text fields we have 8px padding [] the input field allows line breaks and adjusts in heights according to that [] the input field spans over the defined width of the "content" column [] existing content of the fields is shown fully. A follow up story will extend this to do text wrapping if needed. [] if fingerprints are uncollapsed, they are immediately in edit mode, too [] The edit button turns into a save button [] When the user clicks on the save button, all entries are saved in their current state. We operate under the assumption that all entity information is in valid wikidata content languages only. [] The save icon disappears and the edit icon will be shown again [] The page is back in reading mode [] The edit and save buttons follow the following design specifications: (BUT if this is unexpectantly not easy or timeconsuming, please stop) [] colors: default: #3366cc, hover: #447ff5 (not relevant for touch, but for people using mobile on desktop), active (upon clicking the button for 0,5 s): #2a4b8d [] If other changes had been made since the users started editing, the new info is reflected when the saved object is shown, without any extra notice to the user [] The new editing behavior does not interfere with general edit conflict detection **Mocks** [[ https://www.figma.com/file/g86G4bYOcUoIPwEbN041nq/180607_Termbox-Mobile-Sprint?node-id=724%3A425 | Figma file ]] containing all the design specifications / mocks {F28203334} {F28203336} {F28203341} {F28203345} {F28203344} **Notes** * This story does not contain cancel mode, and does not catch errors * Placeholders are covered in T217000