Closed Bug 227053 Opened 21 years ago Closed 21 years ago

gHistoryStatus has no properties

Categories

(Core Graveyard :: History: Global, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugs4hj, Assigned: neil)

References

Details

Attachments

(2 files, 3 obsolete files)

Steps to reproduce (100%):
a)open the history panel in the sidebar
b)click on a container
c)use arrow down/up keys

Current result:
Error: gHistoryStatus has no properties
Source File: chrome://communicator/content/history/history.js
Line: 164

Expected result: no error

Note: 'gHistoryStatus' is not initialized (null) in the sidebar so there should
a) add a check or b) initiazlize 'gHistoryStatus' with the browser window status
bar.

It's a sidebar panel issue, but history specific, so that's why I selected
"History: Global" as component (hope it's the right component).
Attached patch handle null gHistoryStatus (obsolete) — Splinter Review
Assignee: history → timeless
Attachment #137645 - Flags: review?(neil.parkwaycc.co.uk)
Attached patch Fix several issues (obsolete) — Splinter Review
Building on attachment 137645 [details] [diff] [review], I spotted three further errors:
1. I had switched a test so that delete by host/domain stopped working :-(
2. Expand/Collapse context menus didn't work
3. Closing the history sidebar didn't unload the pref observer
Attachment #137680 - Flags: review?(timeless)
I did not read the patches in detail, so I'll just ask:
Did you consider
http://lxr.mozilla.org/seamonkey/source/xpfe/components/history/resources/history.js#127
? It determines if it's run in the sidebar or in its own window based on if
gHistoryStatus is defined...
Blocks: 131182
Blocks: 215590
Comment on attachment 137680 [details] [diff] [review]
Fix several issues

this is not ipv6 safe...
Attachment #137680 - Flags: review?(timeless) → review+
Attachment #137645 - Attachment is obsolete: true
Attachment #137645 - Flags: review?(neil.parkwaycc.co.uk)
Attached patch Updated for irc comments (obsolete) — Splinter Review
Blocks: 230357
Attached patch Tested :-)Splinter Review
Attachment #137680 - Attachment is obsolete: true
Attachment #138693 - Attachment is obsolete: true
Attachment #138700 - Flags: review?(timeless)
Attachment #138700 - Flags: review?(timeless) → review+
Assignee: timeless → neil.parkwaycc.co.uk
Attachment #138700 - Flags: superreview?(alecf)
Comment on attachment 138700 [details] [diff] [review]
Tested :-)

sr=alecf
Attachment #138700 - Flags: superreview?(alecf) → superreview+
Fix checked in.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Neil, with a build that has your patch I get quite often an exception I never
saw before:
Error: [Exception... "Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsITreeView.getCellText]"  nsresult: "0x80070057
(NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
chrome://communicator/content/history/history.js :: historyOnSelect :: line 157"
 data: no]
Source File: chrome://communicator/content/history/history.js
Line: 157

E.g. when in "group by none" mode and deleting an entry using the context menu
or the "Edit" menu. Venkman says that currentIndex is -1 when this happens.
Switching group mode gives a similar error, also with reference to this line.

Attached patch Fix -1 issueSplinter Review
Hmmm... did the status bar actually work before?
Comment on attachment 139013 [details] [diff] [review]
Fix -1 issue

OK, so by switching the tests around a bit I can make rowIsContainer true for a
-1 index so it doesn't query for the URL.
Attachment #139013 - Flags: review?(timeless)
Attachment #139013 - Flags: review?(timeless) → review+
Attachment #139013 - Flags: superreview?(alecf)
Comment on attachment 139013 [details] [diff] [review]
Fix -1 issue

sr=alecf
Attachment #139013 - Flags: superreview?(alecf) → superreview+
Fix checked in.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: