beta v103: Save Image fails for inline images in message reader (error: aInitiatingDocument is undefined, contentAreaUtils.js:363)
Categories
(Thunderbird :: Message Reader UI, defect, P3)
Tracking
(thunderbird102 unaffected)
Tracking | Status | |
---|---|---|
thunderbird102 | --- | unaffected |
People
(Reporter: billfalls, Assigned: aleca)
References
(Regression)
Details
(Keywords: regression)
Steps to reproduce:
Right click on image in body of an email to bring up Save Image dialog
Select folder, image format, and filename including extension
Click OK
Actual results:
Dialog closed without an error message but the image was not in the destination folder (Desktop) or in other possible locations I checked, e.g., Documents
This has never happened with earlier beta and release versions I've used for years.
Expected results:
Image should have been saved to desktop (my chosen destination) with the filename I indicated.
Comment 1•3 years ago
|
||
That's right Bill, thanks for reporting this!
Confirming exactly as described for 103.0b2 (64-bit). Odd.
Affects inline images. Workaround: Copy Image, Paste into graphics app like IrfanView, save image from there. That's odd, too.
Wayne, agree with P3/S3?
Wayne or Alex, who could fix this? (consult PTO calendar)
Maybe simple to fix?
aInitiatingDocument is undefined 3 contentAreaUtils.js:363
continueSave chrome://global/content/contentAreaUtils.js:363
internalSave chrome://global/content/contentAreaUtils.js:342
(Async: promise callback)
internalSave chrome://global/content/contentAreaUtils.js:334
saveURL chrome://global/content/contentAreaUtils.js:85
saveImage chrome://messenger/content/nsContextMenu.js:855
oncommand chrome://messenger/content/messenger.xhtml:1
Assignee | ||
Comment 2•3 years ago
|
||
Most likely regressed by bug 1766030, where they added an extra parameter in the internalSave()
and saveUrl()
method, which we use.
This is the culprit: https://hg.mozilla.org/mozilla-central/diff/3a20f51b32894dc56c76fc24606bdf330d21e4c9/toolkit/content/contentAreaUtils.js
Annoying...I'll take care of it.
Assignee | ||
Comment 3•3 years ago
|
||
Turns out we just took care of this in bug 1777323.
Assignee | ||
Updated•3 years ago
|
Description
•