Closed Bug 610187 Opened 14 years ago Closed 6 years ago

Clarify browser-places.js dependencies (was "Error: PlacesMenu is not defined")

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: tabutils+bugzilla, Unassigned)

References

Details

(Keywords: regression)

Version: unspecified → Trunk
Blocks: 560198
Mano, the sidebar does not include global-scripts.inc where PlacesMenu is defined, but it imports browser.js...
I think either we make it use global-scripts.inc (removing the current browser.js and inlineSpellCheckUI.js imports), we move browserPlacesViews.js to PlacesOverlay or we workaround the issue since the sidebar is most likely not needing those views (by checking if PlacesMenu is in scope or by making a mock of it in the overlay).
What's your suggestion?
Blocks: 528884
Keywords: regression
Assignee: nobody → mano
Blocks: 632411
Seems fixed now in FF4 beta 10. At least the Bugzilla sidebar, that has been broken for all FF4 versions, is working now.
No, it's not fixed.
Bug 632411 solved the error, but we really need to clarify browser-places dependencies.
Summary: Error: PlacesMenu is not defined → Clarify browser-places.js dependencies (was "Error: PlacesMenu is not defined")
No longer blocks: 560198
No longer reproducible.
Version 	48.0a1
Build ID 	20160314030215
User Agent 	Mozilla/5.0 (Windows NT 5.1; rv:48.0) Gecko/20100101 Firefox/48.0
Considering this I will mark this issue as Resolved-WORKSFORME. If anyone can still reproduce it, feel free to reopen the issue and provide more information.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
see comment 5.
The error doesn't happen anymore cause we put a workaround for it, but the dependencies problem still exists.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee: asaf → nobody
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: REOPENED → RESOLVED
Closed: 8 years ago6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.