Closed Bug 18985 Opened 25 years ago Closed 25 years ago

Search button does not invoke dialog, but garbage screen capture.

Categories

(SeaMonkey :: General, defect, P1)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: scalkins, Assigned: mozilla)

Details

Saw this on Win build 1999-11-16-09 M12 today
(Did not see this on Linux build today however)

Steps to repro:
1)Launch Seamonkey. When Mozilla comes up, type over default URL and input a
word in this field (i.e. "virus")
2) Click on the Search button to the right of the URL field.

Expected results:
Search Dialog box appears and you are prompted to select a location to search.
The word "virus" is pre-poulated in the Words: Field of the Search dialog.

Actual results: The Search Dialog box never appears. The entire screen including
the picture of Mozilla is "captured" in another window. If you try to move this
"window" it blurs the contents.
This affects AIM also.
Priority: P3 → P1
This was still a problem on Win build 1999-12-08-16 M12. Setting P1 as this is
basic search functionality.
In todays win build, the dialog opens, but the search engine list is missing so
you cannot perform a search (if you do it comes back empty, even when clicking
on the "Check All" button)
QA Contact: leger → paulmac
qa contact to paulmac.  Paul, can you assign to the right person? Thanks.
Assignee: leger → rjc
QA Contact: paulmac → claudius
I think this should start with robert. This works fine with Linux builds from
today.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I believe this was caused by other regressions in the tree which have been
fixed, so marking WORKSFORME since it does (on Windows) using a fresh pull of
the tip.
Status: RESOLVED → REOPENED
Re-opening, this is still a problem on commercial builds *only*, not a problem
with mozilla builds using 12/16 builds on win98.

The list of search engines does not appear. This is fine on linux.

So to summarize, this is a windows only, commercial only problem. And not a m12
stopper, as it is commercial only.
Resolution: WORKSFORME → ---
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → WORKSFORME
I just (around 11 PM on Dec 16, 1999) did a full pull/build of mozilla as well
as the commercial tree and this works fine for me on Windows. Again, marking as
WORKSFORME.
Robert, I feel like a weenie to keep re-opening this, but it still occurs in
today's 12/17 builds. It must be packaging issue that can't be duplicated by
pulling and build the commercial tree.

I did a directory compare and the chrome\search directories are identical
between the mozilla and commercial builds, what else should I look for?

If you want to reproduce this, you can download the seamonkey32.exe installer at
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/current/

suzanne, am I smoking something here or do you still see it also?
Hey Paul, no problemo.  :^)

I downloaded the seamonkey32.exe installer and indeed see the problem, which is
(as you guessed) that none of the files in
      mozilla\xpfe\components\search\datasets
are being packaged up into
      $(DIST)\res\rdf\datasets
which is weird since just pulling/building the mozilla then the ns trees does do
it.

So, that's the problem.  I don't know how to fix it though... can you re-assign
this bug to someone involved with creating the Commercial installer who would
know?
Status: RESOLVED → REOPENED
re-opening
Assignee: rjc → leaf
Status: REOPENED → NEW
Leaf, are you the man??? Just read robert's last comment.
Resolution: WORKSFORME → ---
Assignee: leaf → rjc
does the mozilla/xpinstall/packager/packages-{win,mac,unix} package manifest
have this stuff in it? Since i'm not totally sure what should be getting
packaged where, can you add it, rjc?
Status: NEW → ASSIGNED
Thanks for the pointer, leaf.  Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Marking bug fixed.
Status: RESOLVED → VERIFIED
Verified in Win build 1999-12-22-09 M13
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.