The JS UI should be fairly robust against unexpected or broken data coming from the database or from user input. Failure to render a value or initialize widgets for a statement should not render the rest of the page unusable. Safe points should be implemented on multiple levels, at least after each Snak, but perhaps also after each Statement, statement group, and page section.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Lydia_Pintscher | T96008 Js UI is too sensitive against invalid data (tracking) | |||
Resolved | Lydia_Pintscher | T89698 Non standard calandar model breaks JS UI | |||
Resolved | aude | T92975 UI breaks on UnDeserializable value. | |||
Resolved | thiemowmde | T94905 Adapt ValueView to DataValuesJavaScript 0.7.0 changes | |||
Resolved | thiemowmde | T99231 Release data-values/javascript 0.7.0 | |||
Resolved | aude | T96892 Implement UnDeserializableValue ::toJSON and newFromJSON in DataValuesJavascript | |||
Resolved | aude | T101231 Release ValueView with UnDeserializableValue expert | |||
Resolved | aude | T99914 Implement UnDeserializableValue expert in ValueView | |||
Open | None | T96010 [Story] add invalid calendar model to calendar model selector if present in the data already |