Page MenuHomePhabricator

Modal from "Download" link should should say "Download 3D file" and not present size options
Closed, DeclinedPublic

Assigned To
Authored By
dr0ptp4kt
Jun 12 2017, 9:04 PM
Referenced Files
F8469765: Artboard.png
Jun 16 2017, 11:07 PM
F8469715: image.png
Jun 16 2017, 11:07 PM
F8469767: Artboard Copy.png
Jun 16 2017, 11:07 PM
F8446574: download_modal.png
Jun 12 2017, 9:32 PM

Description

The options toward the bottom of the download modal should, instead of the current links to raster versions, be simplified down to one option, which links to the original file: "Download 3D file".

Here's the existing interface.

download_modal.png (214×617 px, 45 KB)

Event Timeline

dr0ptp4kt updated the task description. (Show Details)
dr0ptp4kt updated the task description. (Show Details)

@Nirzar to provide mock, potentially using OOJS UI.

Without oojs ui...

image.png (448×1 px, 82 KB)

I would like to start using OOJS UI for this dialog for all kinds of media.

Image download with multiple resolution using OOJS UI

Artboard.png (1×2 px, 520 KB)

Dropdown can contain all the resolutions we want.

3D file download with OOJS UI

Artboard Copy.png (1×2 px, 426 KB)

UI components from - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-wikimediaui-ltr-desktop

Success metric: number of downloads on commons.

Note: if the dropdown for resolutions seems like a bad idea as it's hiding options, i can think of showing them upfront somehow. the main goal here is to highlight the main call to action which "Download" since the user has already clicked on "download this file"

We haven't taken on this task yet. The other tasks with designs forthcoming are probably higher priority than this task, but we'll re-assess priority later. Meanwhile, we're working on a number of other 3D tasks, which will keep us busy until the other designs arrive.

Heads up @Nirzar, it appears that the modal is actually being generated from a Gadget, probably not from the MediaWiki core file page layout code. That may mean more technical complexity if we were to take this on. We'd probably have to modify the Gadget itself for there to be any guarantee that the code would be durable so that for example, selector names don't change out from anyone without people noticing.

@dr0ptp4kt sure, adapting OOJS would be great but optional.

dr0ptp4kt lowered the priority of this task from High to Low.Jun 26 2017, 3:48 PM