Closed
Bug 764303
Opened 12 years ago
Closed 12 years ago
Search suggestions not working
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
2012-10-18
People
(Reporter: cvan, Assigned: spasovski)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
86.03 KB,
image/png
|
Details |
Steps to reproduce: 1) Focus the search box. 2) Begin typing a search term. 3) Search suggestions do not appear. NOTE: Reproducible in production and -dev.
Reporter | ||
Comment 1•12 years ago
|
||
Looks like it regressed with this commit: https://github.com/mozilla/zamboni/commit/dd83a8c9
Assignee | ||
Comment 2•12 years ago
|
||
I am sure I tested this extensively but it's possible something was missed.
Assignee: nobody → dspasovski
Reporter | ||
Comment 3•12 years ago
|
||
It looks like you added the suggestions.js back to the Marketplace consumer JS bundle (https://github.com/cvan/zamboni/commit/50a7217) but I still see a few outstanding issues: 1) Icons are not being displayed (http://cl.ly/2s3J1w3h2o0R3l3U111o) since it looks like the icon field was accidentally removed from the JSON (http://cl.ly/1X3F1Y2E0u1X321G0K38) 2) https://marketplace-dev.allizom.org/en-US/search/suggestions?q=basecam is tracebacking: http://cl.ly/3j3B3g0h162m3Q2h1J05
Assignee | ||
Comment 4•12 years ago
|
||
Wow none of that should've been broken by the JS refactoring work. Good catch tho I'll look into it.
Assignee | ||
Comment 5•12 years ago
|
||
Will open a new bug for the traceback, the rest should be OK: https://github.com/mozilla/zamboni/commit/e2e4800
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 6•12 years ago
|
||
Issue is still reproducing in MP-dev https://marketplace-dev.allizom.org/ Screencast for this issue http://screencast.com/t/k5CLFSnScNX
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Cristian Boldan from comment #6) > Issue is still reproducing in MP-dev https://marketplace-dev.allizom.org/ > Screencast for this issue http://screencast.com/t/k5CLFSnScNX This is definitely a different bug. Please open a new one.
Reporter | ||
Comment 8•12 years ago
|
||
This looks like the issue you were talking about on Android - right, Basta and Davor?
Reporter | ||
Comment 9•12 years ago
|
||
Krupa's filing a new bug.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 10•12 years ago
|
||
The original bug described by cvan is reproducible again on desktop,for both staging and production.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 11•12 years ago
|
||
here is the test video from automation: https://saucelabs.com/jobs/f59bf0f5854a4cfcbe17e41f16dfc83c#
Assignee | ||
Comment 12•12 years ago
|
||
done: https://github.com/mozilla/zamboni/commit/cb7e70a
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 13•12 years ago
|
||
Issue still reproducible on latest FF Nightly.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 14•12 years ago
|
||
This bug has changed quite a bit over its lifespan. Victor: Is the issue still the same as the one demonstrated in comment #11, or is it a different kind of broken? I'm also curious as to whether the WD failure may be a separate issue. I.e.: perhaps WebDriver fires off a different event/change than the one we're listening for to trigger search suggestions. It's not inconceivable that the way we're polling for updates isn't automation-friendly.
Assignee | ||
Comment 15•12 years ago
|
||
we pushed a new fix: https://github.com/mozilla/zamboni/commit/30d7b65
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 17•12 years ago
|
||
Updated•12 years ago
|
Target Milestone: 2012-06-14 → 2012-10-18
You need to log in
before you can comment on or make changes to this bug.
Description
•