Closed Bug 819365 Opened 12 years ago Closed 12 years ago

[desktop] Search is not working as expected after opening an app from search suggestion list

Categories

(Marketplace Graveyard :: Consumer Pages, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
2012-12-20

People

(Reporter: vcarciu, Assigned: spasovski)

References

()

Details

Prerequisites:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20121202 Firefox/20.0

Steps to reproduce:
1.Go to MP and enter a search term in search box(eg. "solit")
2.Directly from search suggestion list, open an app(eg. Solitaire)
3.In the search box, delete the "solit" term and enter another one for which no results should be displayed and press Enter.

Expected results:
No results found message should be displayed

Actual results:
Nothing happens and the user is still on details page of Solitaire

Please see screencast for this bug: http://screencast.com/t/4TXfWTNa

NOTES:
The bug is only reproducible if the apps are opened from search suggestion lists. For the apps opened from another places everything is working as expected and "No results found" message is displayed.
I can't reproduce this.
Summary: [desktop]Search is not working as expected after opening an app from search suggestion list. → [desktop] Search is not working as expected after opening an app from search suggestion list
Whiteboard: [janus]
The install button in the details page in step #2 also changes to "Launch"
(In reply to Chris Van Wiemeersch [:cvan] from comment #1)
> I can't reproduce this.

I am still able to reproduce it as described in the initial scenario. Please let me know if you need any other additional information.
I don't have a searchbox on my detail pages (?) and can't reproduce this.  Krupa - can you work with cvan to reproduce it?
Yeah, Krupa showed me. Some strange ish.
Assignee: nobody → cvan
Assignee: cvan → dspasovski
Target Milestone: 2012-12-13 → 2012-12-20
done: https://github.com/mozilla/zamboni/commit/d6a6e86
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified and it is not reproducible anymore on -dev, but it is still reproducible in production.

Will this change be applied only at next push? If yes, please feel free to close it again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This was fixed after our push to production (2012-12-13 15:27:24 PST).
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
(In reply to Chris Van Wiemeersch [:cvan] from comment #8)
> This was fixed after our push to production (2012-12-13 15:27:24 PST).

Marking it as verified then.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.