Closed Bug 997976 Opened 12 years ago Closed 12 years ago

Regression: Error: Invalid Places node when click / middle click / press enter Livebookmark And Livebookmark container do not expand in Sidebar

Categories

(Toolkit :: Places, defect)

Product:
Toolkit
Component:
Places
Version:
31 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla31
Tracking Flags:
Tracking Status
firefox30 --- unaffected
firefox31 + verified

People

(Reporter: alice0775, Unassigned)

References

Details

(Keywords: regression, ux-consistency)

STR middle click Livebookmark AR: Nothing happen with error, Error: Error: Invalid Places node Source File: resource://gre/modules/PlacesUtils.jsm Line: 446 ER: Open in new tab Regression: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=84536adf6109&tochange=e71ed4135461 Suspect: Bug 330879 No automated test???
And Error: Error: Invalid Places node Source File: resource://gre/modules/PlacesUtils.jsm Line: 197
left click and press enter also nothing happen
Summary: Regression: Error: Invalid Places node when middle click Livebookmark → Regression: Error: Invalid Places node when click / middle click / press enter Livebookmark
And Click livebookmark container in Sidebar also nothing happen. Click livebookmark container in Sidebar tree should be expanded. Error: A promise chain failed to handle a rejection. Full Message: Error: Invalid Places node Source File: resource://gre/modules/PlacesUtils.jsm Line: 184 Source Code: 184
Summary: Regression: Error: Invalid Places node when click / middle click / press enter Livebookmark → Regression: Error: Invalid Places node when click / middle click / press enter Livebookmark And Livebookmark container do not expand in Sidebar
we will backout bug 330879, the problem is the nature of live bookmarks nodes. and no, we don't have an automated test covering live bookmarks UI functionality.
I backed out the patch in bug 330879.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
status-firefox31: affected → fixed
Target Milestone: --- → mozilla31
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 Reproduced in Nightly 31.0a1 2014-04-17. Verified as fixed in Firefox 31 beta 4.
Status: RESOLVED → VERIFIED
status-firefox31: fixed → verified
Keywords: verifyme
QA Contact: petruta.rasa
You need to log in before you can comment on or make changes to this bug.