Closed Bug 591807 Opened 14 years ago Closed 13 years ago

Error while selecting bookmark in BM without any other window open

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-seamonkey2.1 -)

RESOLVED FIXED
seamonkey2.2
Tracking Status
blocking-seamonkey2.1 --- -

People

(Reporter: stefanh, Unassigned)

References

Details

STR: 1) Get a mac, launch SeaMonkey 2) Close any open windows 3) From the main menu bar, select "Manage Bookmarks..." 4) In the BM window select a bookmark --> an error in the js console appears, indicating code that relies on an open browser window: Error: event is not defined Source File: file:///Users/Stefan/objdir-sm-trunk/mozilla/dist/SeaMonkeyDebug.app/Contents/MacOS/components/nsMicrosummaryService.js Line: 1982
Oh, right - forgot to say that this assumes that bug 586363 is resolved, since atm the BM won't open at all if all windows are closed.
Depends on: 586363
Hmm, the microsummary service is a toolkit component. Does Firefox still have the same hiddenWindow stuff? Is this happening there as well?
Firefox has a slightly different implementation of the hiddenwindow stuff, so I'm not sure we can rely on toolkit doing the right thing here.
blocking-seamonkey2.1: --- → ?
I suppose the question is whether it does happen in Firefox, if it does then this bug or a clone should be put against firefox/toolkit. Either way I don't think we can block on this but if we get a fix we should try and take it.
blocking-seamonkey2.1: ? → -
Bug 524091 removed microsummaries support, including the cited file. I guess we need to open a bug about removing all traces from our code and then investigate closing this one. Before I file such a bug, I think the Council should decide whether that's OK or the feature should be kept (in which case we would have to maintain it; just asking for "better safe than sorry").
The backend was removed including the toolkit components. So the front end UI code in /suite/ doesn't work anyway.
(In reply to comment #6) > The backend was removed including the toolkit components. So the front end > UI code in /suite/ doesn't work anyway. Yes, as I said. My questions was whether anyone intends to bring it back (to suite land) or that removal bug should be filed.
Microsummaries are/were never really used in any way broadly and removing simplifies code, I'd suggest following that and also removing all traces of it in SeaMonkey.
When I say backend I include the removal of code from the CPP widget code. It's hard to see how that can be brought into the Suite. > Microsummaries are/were never really used in any way broadly and removing > simplifies code, I'd suggest following that and also removing all traces of it > in SeaMonkey. Agreed.
Depends on: 659277
Filed bug 659277 for the removal. Once that is fixed, this one can be closed.
Stefan, please check again with the next trunk nightly, then resolve if the error is gone.
Bah, make that "the next trunk nightly that contains the full fix for bug 659277"...
(In reply to comment #11) > Stefan, please check again with the next trunk nightly, then resolve if the > error is gone. Yeah, it's gone. Resolving as fixed, since bug 659277 obviously fixed it ;-)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.2
You need to log in before you can comment on or make changes to this bug.