Closed Bug 1267991 Opened 10 years ago Closed 8 years ago

Error in Browser Console when using Undo feature in Library

Categories

(Firefox :: Bookmarks & History, defect, P3)

Product:
Firefox
Component:
Bookmarks & History
Platform:
x86_64
Windows 7
Type:
defect

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: Virtual, Unassigned)

Details

(Keywords: nightly-community)

When I want to use Undo (CTRL+Z keyboard shortcut) feature in Library, mostly after adding a new bookmark, sometimes I see this error in Browser Console: 13:07:33.323 An error occurred executing the cmd_undo command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITransactionManager.undoTransaction]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://browser/content/places/controller.js :: PC_doCommand :: line 220" data: no] goDoCommand()globalOverlay.js:103 oncommand()places.xul:1 1globalOverlay.js:103
Priority: -- → P3
Yesterday I got these 2 errors in Browser Console with same STR from Comment #0: > NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITransactionManager.undoTransaction] controller.js:217 > PC_doCommand chrome://browser/content/places/controller.js:217:9 > goDoCommand chrome://global/content/globalOverlay.js:93:7 > oncommand chrome://browser/content/places/places.xul:1:1 > An error occurred executing the cmd_undo command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITransactionManager.undoTransaction]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://browser/content/places/controller.js :: PC_doCommand :: line 217" data: no] globalOverlay.js:95 > goDoCommand chrome://global/content/globalOverlay.js:95:5 > oncommand chrome://browser/content/places/places.xul:1:1
Has STR: --- → yes
I have not seen these errors in Browser Console for a long time, so I'm closing this bug as WORKSFORME.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.