Closed
Bug 68979
Opened 24 years ago
Closed 23 years ago
cnbc.com - "Search by Relevance" button doesn't fire
Categories
(Tech Evangelism Graveyard :: English US, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: benc, Assigned: zach)
References
()
Details
Actually, any search result from the "career center" page results in a search
result page w/ a button that doesn't work.
I tested the same link in Comm 4 and it works.
Sent feedback to the site, will post when it arrives.
Reporter | ||
Comment 1•24 years ago
|
||
Dear Valued CNBC.com Site User,
Thank you for your interest in the CNBC.com website.
We apologize for the inconvenience caused. Please note that our site is best
viewed using the Netscape browser Version 4.7. Hence, we suggest that using
this version of Netscape may resolve the problem that you are experiencing.
Please contact us with any additional questions or concerns that you may have.
Sincerely,
Grace
CNBC.com
Customer Service Support
Assignee | ||
Comment 2•24 years ago
|
||
erg. I just sent off a 'fright-o-gram' to them. Lets hope that fixes it.
Assignee | ||
Updated•24 years ago
|
Assignee: evangelism → zach
Priority: -- → P2
Assignee | ||
Comment 4•24 years ago
|
||
Still haven't gotten a firght-o-gram responce yet, taking bug and giving
100% to it!.
Comment 5•23 years ago
|
||
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
Comment 6•23 years ago
|
||
cnbc is now part of msn I think. this server no longer exists. -> fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Summary: "Search by Relevance" button doesn't fire → cnbc.com - "Search by Relevance" button doesn't fire
Comment 7•23 years ago
|
||
Well the page is gone and I can't find it thru anywhere on the site. Should
maybe be invalid now but verifying fixed.
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•