Change Details

Per this [community feedback comment](https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#c-Jonesey95-20251107012100-EBlackorby-WMF-20251106223800), we may need to include license information alongside the images we are displaying in the new ImageBrowsing feature – at least in the DetailView (when a given image is expanded at the top). Let's explore how best to do that in a way that causes minimal disruption to the rest of the feature. Ideally this is a change that can be deployed *after* the current A/B test is complete (we don't want to make significant user-facing changes mid-test). But we should start this work soon so it's ready if we need to move before then. ==== Design @JScherer-WMF to add some mockups of an updated Detail View which includes license info. Some things to consider: * We already make an `imageinfo` API call (which can provide this license data) in the DetailViewControls component (the buttons in the lower right hand corner of the big image). Ideally we can just add license info to this component. We could use an icon button (indicating basic license type – public domain, creative commons, etc) plus an expandable popover containing more details (similar to how downloads work) if we want to be really economical in terms of space. ==== Implementation * Data should be available in an `imageinfo` API call * This is fine for the single detail view image but would be problematic if we have to do it for every VTOC item at once (the response needs to parse wikitext first, so there are perf concerns) * Images from other wikis – how can we ensure that license data for these images appears in the correct language? * Can we use Wikidata license information if available? * Where should we actually link to? * There is prior art in desktop and mobile MediaViewer that we could look at too ==== Next steps - [ ] @JScherer-WMF to provide some mockups here in the task description - [ ] One of the engineers can begin exploration once we have mockups - [ ] Product and legal should determine whether we can wait to the conclusion of the current A/B test to add this feature, or whether it must happen sooner.

Per this [community feedback comment](https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#c-Jonesey95-20251107012100-EBlackorby-WMF-20251106223800), we may need to include license information alongside the images we are displaying in the new ImageBrowsing feature – at least in the DetailView (when a given image is expanded at the top). This is a change that can be deployed *after* the current A/B test is complete (we don't want to make significant user-facing changes mid-test). But we should start this work soon so it's ready if we need to move before then. ==== Design {F70293069} {F70293070} [] Caption line height should shrink by 1, to make room for license [] There should be a license link below the caption (insofar there is one), in the same color as the caption [] License name (e.g. CC BY 4.0) should be shown [] License should link to the license section of the file page

Per this [community feedback comment](https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#c-Jonesey95-20251107012100-EBlackorby-WMF-20251106223800), we may need to include license information alongside the images we are displaying in the new ImageBrowsing feature – at least in the DetailView (when a given image is expanded at the top). Let's explore how best to do that in a way that causes minimal disruption to the rest of the feature. Ideally thisThis is a change that can be deployed *after* the current A/B test is complete (we don't want to make significant user-facing changes mid-test). But we should start this work soon so it's ready if we need to move before then. ==== Design @JScherer-WMF to add some mockups of an updated Detail View which includes license info. Some things to consider: * We already make an `imageinfo` API call (which can provide this license data) in the DetailViewControls component (the buttons in the lower right hand corner of the big image). Ideally we can just add license info to this component. We could use an icon button (indicating basic license type – public domain, creative commons, etc) plus an expandable popover containing more details (similar to how downloads work) if we want to be really economical in terms of space.{F70293069} ==== Implementation{F70293070} * Data should be available in an `imageinfo` API call * This is fine for the single detail view image but would be problematic if we have to do it for every VTOC item at once (the response needs to parse wikitext first[] Caption line height should shrink by 1, so there are perf concerns)to make room for license * Images from other wikis – how can we ensure that license data fo[] There should be a license link below the caption (insofar these images appearsre is one), in the same correct language?lor as the caption * Can we use Wikidata license information if available?[] License name (e.g. CC BY 4.0) should be shown * Wher[] License should we actually link to?link to the license section of the file page * There is prior art in desktop and mobile MediaViewer that we could look at too ==== Next steps - [ ] @JScherer-WMF to provide some mockups here in the task description - [ ] One of the engineers can begin exploration once we have mockups - [ ] Product and legal should determine whether we can wait to the conclusion of the current A/B test to add this feature, or whether it must happen sooner.