Closed Bug 1245904 Opened 9 years ago Closed 5 years ago

Selecting attachments should allow access to all attachments

Categories

(developer.mozilla.org Graveyard :: File attachments, defect)

Product:
developer.mozilla.org Graveyard
Component:
File attachments
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: sheppy, Unassigned)

References

Details

(Keywords: in-triage, Whiteboard: [specification][type:change])

What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== Currently, when you're given a list of files, you only see files that are currently considered part of the page you're looking at: files you have uploaded during your current session and/or are already linked to on the page. When the UX requires selecting a file, we should make it possible to see not only those uploaded "to the current page" but those uploaded to other pages, with the ability to search for attachments by matching on names, filenames, and/or descriptions. What problems would this solve? =============================== This prevents easy re-use of existing files, so we have tons of duplicates. This would also make it easier in general to use attachments and likely would make more pages use them better. Who would use this? =================== Anyone editing content that wants to use files or images. What would users see? ===================== A more advanced file picking UX with search and such. This needs some UX love. What would users do? What would happen as a result? =================================================== Select a file, hopefully avoiding uploading a dupe. Is there anything else we should know? ======================================
Blocks: mdn-attachments
(In reply to Eric Shepherd [:sheppy] from comment #0) > This prevents easy re-use of existing files, so we have tons of duplicates. I would like to understand why having duplicates is a problem: 1. I've heard that the size of our DB is not a big deal during last dev meeting, so I don't think it is a problem for the devs (they may disagree with me) 2. I don't see a use case where preventing duplicate is a good thing from our side; more I think it is a risk: having the same images used in several places make it complex to delete or update it as we need to understand all its uses.
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.