Last modified: 2014-03-11 10:18:53 UTC
When clicking "edit" on a claim that is based on a non-existing property, the expected behavior is that deleting the claim should be possible, but editing it should not even be attempted. Currently, at least for some data types (like Time), the behavior is erratic: the first click on "edit" does nothing [1], the next one opens edit mode, but doesn't disable the edit buttons for other claims. Canceling works, but then, clicking on "edit" again does nothing again [2]. Only clicking a fourth time opens edit mode again (again with all other "edit" links staying enabled). If the property (and thus the data type) isn't know, editing should not be possible or attempted (though edit mode should still be possible for at least removing the claim, and possible also for sorting). The same is true for qualifiers and reference snaks, of course. It's probably nice to at least try to show the value, based on the value type. (Ideally, we would record the data type in the snak, so we would have sufficient information for rendering, and maybe even for assigning a new property to the claim). [1] Error: No sufficient purpose provided for choosing a parser @ http://localhost/daniel/wikidata/extensions/DataValues/DataValuesCommon/js/src/ValueParsers/ValueParserFactory.js:125 [2] Error: No adequate information to find a parser @ http://localhost/daniel/wikidata/extensions/DataValues/ValueView/resources/jquery.valueview/valueview.valueview.js:606
