**Mock**
!!TODO!!
**Acceptance Criteria**
[] If there has not been any activity after !!TODO X!! seconds of editing a label or description field, or if the user leaves the field, it is evaluated if label and description of this language now have the same contents.
[] If they have the same content, an error message appears under the description field.
[] This error message is blocking the publishing process, but not the editing of the fields
[] If the save cannot be executed because of a validation error, the user's viewport is scrolled to contain the start of the monolingual fingerprint view with the faulty area at the top. If there are two areas, the user is scrolled to the first instance
[] Once the information is not redundant anymore (check happens as explained above) the message disappears
---------------
**Old stuff**
//Ticket not prepped yet, these are @Pablo-WMDE 's thoughts from T219886#5160537 /
There was some discussion around T212869, the check for label and description, today and it turns out this is actually a check , having a the same label and description in any given language - so something that would be perfect for in-form validation. A beauty of this is that we can - of course - detect this in real time without an API request. A change that we did for lexeme comes to mind - try [[ https://wikidata.beta.wmflabs.org/w/index.php?title=Lexeme:L42 | here ]] to add another lemma in language "de" and see what happens.
{F28941818}