Closed Bug 68681 Opened 24 years ago Closed 24 years ago

History window empty

Categories

(Core Graveyard :: History: Global, defect)

x86
All
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tracy, Assigned: waterson)

References

Details

(Keywords: smoketest)

seen on commercial builds:

windows 2001-02-13-06-mtrunk
linux 2001-02-13-06-mtrunk
mac 2001-02-13-04-mtrunk

-go to Tasks | Tools | History

this page opens empty even after a full session of browser use.

this window should show history for time specified in preferences (ie.. last 5 
days)
Keywords: smoketest
I just made a linux build from CVS - is mailnews empty too?
mail worked fine on the noted builds.
Ugh, I'm seeing this on linux too.
nothing was checked into history yesterday.. mailnews and bookmarks are NOT
blank either, so it's (probably) not a tree problem.
I'm making no traction on this though, and I checked in nothing that had to do
with history or trees. Looking for help!
here, alternate three-pane is clean empty, whilst default pane setup is OK.
ok, I've traced this all through global history.. I can't find anything wrong.
RDF notifications are happening, everything seems to be just peachy. reassign to
waterson (I think it's RDF..could be XUL) while I drive into work, cc hyatt

by the way, I tried backing out waterson's latest changes to the template
builder, still no love.
Assignee: alecf → waterson
oops, CC hyatt
This effects the address book and a commercial component as well. They are all
empty. 
Linux SEA 2001021308: Alternate threepane empty. Asa also saw this.
*** Bug 68701 has been marked as a duplicate of this bug. ***
Blocks: 39054
history, AB and alternate threepane now OK again on a new CVS build, linux.
waterson fixed this by backing himself out, so I'll mark fixed for him.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified fixed on commercial builds:

windows 2001-02-13-06-mtrunk
linux 2001-02-13-06-mtrunk
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.