Closed Bug 1253095 Opened 9 years ago Closed 9 years ago

Attachment upload lost upon edit conflict

Categories

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

All
Other
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: krenair, Unassigned)

References

Details

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

What did you do? ================ 1. Open the edit page in two separate tabs 2. Make a change in one, save 3. Upload a file in the other, add link to it, attempt to save 4. Observe edit conflict screen What happened? ============== Attachment upload not listed What should have happened? ========================== Attachment upload listed Is there anything else we should know? ======================================
Severity: normal → minor
Component: Editing → File attachments
Keywords: in-triage
This is basically moot now that the file upload will reload the edit page after success and not use AJAX anymore to stay on the page. Having multiple tabs open is still an issue of course in the sense that each has its state of the editing UI once loaded, but removing AJAX from that at least doesn't make it more complicated anymore. We can't currently refresh the list of attachments available in the editor plugin as that's out of scope of the plugin and the backend should not gain an API to provide that list on demand to not accidentally leak private information. If you want to use a file uploaded in one tab in a second tab, reload the second tab to see it appear in the editor file plugin. Alternatively, copy the full URL of the newly uploaded file from tab 1 and use the URL to add it in tab 2 (via the article source or editor file plugin doesn't matter). Once saved the backend will find the file referenced in the content and goes to make the book keeping that the file was linked in the article. Closing as fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.