User story
As a normal user
I want to be able go to the File page
And view existing Q-item values for a non-depicts property
We have this
<undefined current behavior>
We want this
At the very least we should make sure non-depicts statements don't break the page
Acceptance Criteria
Test case set up at https://commons.wikimedia.beta.wmflabs.org/wiki/File:T219381.png
On the File page
- Existing non-depicts statements should be rendered so that we can spot vandalism
- They should be rendered differently (e.g. lighter/grayed out) so that it's obvious they are non-standard statements (for now)
- Non-depicts statements need to be rendered in a way that makes sense: i.e. no obvious issues
- These statements must not affect captions or depicts statements, which should continue to work as expected
Original ticket description below:
If a user creates a statement using an unsupported wikidata property (i.e. anything except 'depicts') what should we do?
At the very least we should make sure it doesn't break the page - our js isn't really set up for handling non-depicts statements on the page, so I'm not sure what the js will do if a non-depicts statement appears in the DOM (the php will show it by default)
We may need to turn off display of non-depicts statements entirely (via php)
@Ramsey-WMF this needs to be considered for the crawling release (even if we decide not to do it we do need to think about it)