Steps to reproduce: - open a page with a download link - perform a right-click on the link to open up the context menu - click the "Save Link As ..." Expected result: - A choose-directory popup should open and after choosing the target directory, the download should start Actual result: - Nothing happens. --- This is what I see in my OSX terminal console: ➜ MacOS WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts). pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14 nsContextMenu.prototype.saveHelper@chrome://browser/content/nsContextMenu.js:1247:26 nsContextMenu.prototype.saveLink@chrome://browser/content/nsContextMenu.js:1290:5 oncommand@chrome://browser/content/browser.xul:1:1 This is what I see in the BrowserConsole: unsafe CPOW usage nsContextMenu.js:1281:0 unsafe CPOW usage utilityOverlay.js:391:0 unsafe CPOW usage utilityOverlay.js:395:0 unsafe CPOW usage utilityOverlay.js:397:0 unsafe CPOW usage utilityOverlay.js:407:0 unsafe CPOW usage utilityOverlay.js:413:0 unsafe CPOW usage utilityOverlay.js:414:0 unsafe CPOW usage utilityOverlay.js:417:0 unsafe CPOW usage nsContextMenu.js:1247:0 unsafe CPOW usage PrivateBrowsingUtils.jsm:22:0 unsafe CPOW usage PrivateBrowsingUtils.jsm:49:0 unsafe CPOW usage PrivateBrowsingUtils.jsm:28:0 unsafe CPOW usage nsContextMenu.js:1263:0 NS_ERROR_XPC_CANT_PASS_CPOW_TO_NATIVE: It's illegal to pass a CPOW to native code arg 0 [nsIHttpChannel.referrer] nsContextMenu.js:1263:0

Additional notes: if I choose "save link as", no UI appears (e.g. in the downloads panel) but if I then try to quit, I get a dialog "If you exit now, N downloads will be canceled. Are you sure...". (Windows)

Can you still reproduce it in latest Nightly after bug #1127927 was fixed? If not, I will mark this bug as duplicate.

(In reply to Virtual_ManPL [:Virtual] from comment #4) > Can you still reproduce it in latest Nightly after bug #1127927 was fixed? > If not, I will mark this bug as duplicate. Testing with the latest nightly, I can no longer reproduce this bug - seems like it is fixed now :) Note that I am not sure what the correct status of the bug should be now (FIXED - WORKSFORME?), so I left the status to "NEW" for now.

Thank you very much for checking.