Closed
Bug 86737
Opened 24 years ago
Closed 24 years ago
search is broken
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
MOVED
People
(Reporter: jay, Assigned: leaf)
References
Details
(Keywords: regression, smoketest)
Attachments
(1 file)
|
59.06 KB,
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en]C-AOLNSCP (Win98; U)
BuildID: 2001061911
Using URL bar search doesn't work. I have seen a few different symptoms with
today's builds (both 2001061901 and 2001061911).
With the 2001061911 build, the search button doesn't work at all. If I type in
something and click it, nothing happens.
Can someone please confirm this with today's builds. This seems like a major
regression, and is definitely a smoketest blocker!
Reproducible: Always
Steps to Reproduce:
1. Create new profile
2. Enter words into URL bar (with sidebar closed)
3. Click Search button next to URL bar
Actual Results: With 2001061901, the button seems to work ok, but the sidebar
doesn't show any results. Also, in the prefs, you cannot change the default
search engine, as there are no items in the drop down menu (when typing into the
url bar, the dropdown menus says "Search undefined for 'search words'".
With the 2001061911 build, the search button doesn't work at all. If I type in
something and click it, nothing happens.
| Reporter | ||
Comment 1•24 years ago
|
||
adding regression and smoketest keywords.
Keywords: regression,
smoketest
Using 2001-06-19-11-trunk/ on WinNT 4.0
I converted my existing 4.x profile.
I tried entering 'tv' in the url bar and hit search button
and nothing happens. Button lettering changes
from black to white when I click on it but it doesn't
kick off the search.
Also when I converted my profile, all side bar tabs were missing
With a brand new profile, my sidebar tabs are there but search
still fails as it exhibits the same behavior I mentioned above.
hope this helps.
Looks like the searchplugin directory is not getting created on windows.
this is working on my builds so it's on the install that we are breaking.
Comment 6•24 years ago
|
||
can someone attach an install log?
Comment 7•24 years ago
|
||
Broke between the 2001-06-18-07 and 2001-06-18-09 builds apparently.
Investigating...
samir's comments
"today's mozilla's regus.xpi holds the searchplugins dir just fine."
this seems like a build issue. Over to build team.
Assignee: matt → jj
Comment 10•24 years ago
|
||
Note:
1> Mozilla is not broken: mozilla's regus.xpi contains the searchplugins
directory. Please move this bug to busgcape.
2> Nothing remotely related to this problem changed in mozilla *or* ns during
the cited time that this was caused. Build/config issue?
Comment 11•24 years ago
|
||
http://bugzilla.mozilla.org/show_bug.cgi?id=86683 is probably related to this.
Those affected can't see mail headers and all pref defaults are from mozilla
rather than NS. It also works on the 6-18-07 build but not the 6-18-09 build.
Comment 12•24 years ago
|
||
windows build system -> Leaf
Assignee: jj → leaf
Component: Search → Build Config
QA Contact: claudius → granrose
Comment 13•24 years ago
|
||
turns out the commercial installer doesn't seem to be packaging the commercial
prefs files (mailnews-ns.js, etc) starting yesterday or the day before. That's
causing us lots of problems and could cause this problem too.
Comment 14•24 years ago
|
||
Bug moved to http://bugscape.netscape.com/.
If the move succeeded, asa@mozilla.org will receive a mail
containing the number of the new bug in the other database.
If all went well, please mark this bug verified, and paste
in a link to the new bug. Otherwise, reopen this bug.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → MOVED
Comment 15•24 years ago
|
||
this bug is now http://bugscape/show_bug.cgi?id=6644
I have moved the bug and carried over the attachment.
Status: RESOLVED → VERIFIED
| Assignee | ||
Comment 16•24 years ago
|
||
*** Bug 86683 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•6 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•