Closed
Bug 581076
Opened 14 years ago
Closed 14 years ago
No "See all results" link present when searching for add-ons and not all are displayed (extensions.getAddons.maxResults)
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla2.0b7
Tracking | Status | |
---|---|---|
blocking2.0 | --- | beta7+ |
People
(Reporter: whimboo, Assigned: Unfocused)
References
Details
(Keywords: regression, Whiteboard: [strings])
Attachments
(2 files, 4 obsolete files)
48.32 KB,
image/png
|
Details | |
18.97 KB,
patch
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b2) Gecko/20100720 Firefox/4.0b2 Search for add-ons will return a list of found add-ons from AMO. If the number exceeds the limit (set by extensions.getAddons.maxResults), there is no link shown, the user can click to get forwarded to AMO. Users will be stuck and don't know where they can get the wanted add-on if it isn't present in the current list. Steps: 1. Open about:config and set i.e. set extensions.getAddons.maxResults=4 2. Search for "url" After step 2 the expected 4 results should be displayed but it's hard to get to the real list of all found add-ons. Right now, you will have to go to AMO manually and start a search again.
Comment 1•14 years ago
|
||
Boriss needs to look at this, don't think it will be a blocker though.
Keywords: uiwanted
Comment 2•14 years ago
|
||
Actually, I'd call this blocking. The link between AMO and the add-ons manager isn't one most users will be aware of, so failing to locate an add-on in the manager means the user might: 1. Give up. "This add-on must not exist." 2. Keep trying different searches, which may eventually lead to the desired add-on. Now the user knows the list of results is incomplete and that trying different combinations of black magic strings may actually produce the desired result. Instead, if the user has a link to AMO, they can get the full list of results, hopefully find the add-on they want more easily, and can explore AMO if they'd like to search for a type of add-on rather than one in particular. This link could just be the final item in the list of results (see attached)
Updated•14 years ago
|
Assignee: nobody → bparr
blocking2.0: ? → beta4+
Reporter | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > Created attachment 460306 [details] > sketch: see all results The author is a left over, right? AFAIK we cannot display it for search results. > 2. Keep trying different searches, which may eventually lead to the desired > add-on. Now the user knows the list of results is incomplete and that trying > different combinations of black magic strings may actually produce the desired > result. Which can also be difficult because of bug 581103. Given search terms do not always show up the expected results right now. > Instead, if the user has a link to AMO, they can get the full list of results, > hopefully find the add-on they want more easily, and can explore AMO if they'd > like to search for a type of add-on rather than one in particular. In Namoroka we also show the total count of search results behind that string. Do we also wanna have it in the new add-ons manager? I would vote for that, because we have the information and it will give the user a much more detailed view of what is available.
Updated•14 years ago
|
Assignee: bparr → bmcbride
Assignee | ||
Comment 5•14 years ago
|
||
Attachment #469762 -
Flags: review?(dtownsend)
Comment 6•14 years ago
|
||
Comment on attachment 469762 [details] [diff] [review] Patch v1 More context would be better. >@@ -73,3 +73,6 @@ enableAddonTooltip=Enable this add-on > enableAddonRestartRequiredTooltip=Enable this add-on (restart required) > disableAddonTooltip=Disable this add-on > disableAddonRestartRequiredTooltip=Disable this add-on (restart required) >+ >+#LOCALIZATION NOTE (showAllSearchResults) %S is the total number of search results >+showAllSearchResults=See all %S results This needs to go through the plural form stuff. >diff --git a/toolkit/mozapps/extensions/content/extensions.js b/toolkit/mozapps/extensions/content/extensions.js > if (aIsRemote) > gCachedAddons[aObj.id] = aObj; > >- self._listBox.appendChild(item); >+ self._listBox.insertBefore(item, self._listBox.lastChild); insert before _allResultsLink
Attachment #469762 -
Flags: review?(dtownsend) → review-
Assignee | ||
Comment 7•14 years ago
|
||
(In reply to comment #6) > >+ self._listBox.insertBefore(item, self._listBox.lastChild); > > insert before _allResultsLink As discussed on IRC: These aren't actually the same nodes. So ignoring that.
Assignee | ||
Comment 8•14 years ago
|
||
Added PluralForm stuff. Fixed the themes - I had accidentally only changed winstripe. And discovered a bug where doing a search, switching views, and re-doing the same search would result in the link not showing. Fixed that (needed some refactoring) and added a test for it. (In reply to comment #6) > More context would be better. Sorry, I thought I had that set to something better than it was.
Attachment #469762 -
Attachment is obsolete: true
Attachment #470091 -
Flags: review?(dtownsend)
Updated•14 years ago
|
Attachment #470091 -
Flags: review?(dtownsend) → review+
Assignee | ||
Comment 9•14 years ago
|
||
Attachment #470091 -
Attachment is obsolete: true
Comment 10•14 years ago
|
||
needs rebase: anarchy ~/code/moz/mozilla-central/push-only/mozilla % hg qimport "https://bug581076.bugzilla.mozilla.org/attachment.cgi?id=470127" -n "see-all-results" adding see-all-results to series file anarchy ~/code/moz/mozilla-central/push-only/mozilla % hg qpush applying see-all-results patching file browser/app/profile/firefox.js Hunk #1 FAILED at 50 1 out of 1 hunks FAILED -- saving rejects to file browser/app/profile/firefox.js.rej patching file toolkit/mozapps/extensions/content/extensions.js Hunk #2 FAILED at 1127 1 out of 6 hunks FAILED -- saving rejects to file toolkit/mozapps/extensions/content/extensions.js.rej patching file toolkit/mozapps/extensions/content/extensions.xul Hunk #1 FAILED at 212 1 out of 1 hunks FAILED -- saving rejects to file toolkit/mozapps/extensions/content/extensions.xul.rej patching file toolkit/mozapps/extensions/test/browser/Makefile.in Hunk #1 succeeded at 56 with fuzz 1 (offset 1 lines). patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh see-all-results
Updated•14 years ago
|
Whiteboard: [4b2] → [4b2][needs-rebase]
Assignee | ||
Comment 11•14 years ago
|
||
Rebased, and fixed the test to work again, after bug 562797 removed the callback to loadView()
Attachment #470127 -
Attachment is obsolete: true
Assignee | ||
Comment 12•14 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/6fe388a0fb5e
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Flags: in-litmus-
Resolution: --- → FIXED
Whiteboard: [4b2][needs-rebase]
Target Milestone: --- → mozilla2.0b5
Assignee | ||
Comment 13•14 years ago
|
||
... and backed out due to test failures. test_AddonRepository.js was failing for some reason - no idea yet how it could do that. Logs: Linux opt: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1283144074.1283144875.30462.gz OSX opt: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1283145114.1283146001.2227.gz
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 14•14 years ago
|
||
Backout changeset was: https://hg.mozilla.org/mozilla-central/rev/0487454f4219
Assignee | ||
Comment 15•14 years ago
|
||
Given I don't know why that test failed, and we're right up against the wire with the freeze - I would rather re-target this for beta6, and land soon after the freeze.
Updated•14 years ago
|
Whiteboard: [strings]
Comment 17•14 years ago
|
||
Comment on attachment 470365 [details] [diff] [review] Patch v2.1 - ready for checkin "See all 1 result", really? I suspect that should rather be "See one result", right?
Assignee | ||
Comment 18•14 years ago
|
||
(In reply to comment #17) > Comment on attachment 470365 [details] [diff] [review] > Patch v2.1 - ready for checkin > > "See all 1 result", really? I suspect that should rather be "See one result", > right? Eh, I guess. Technically, that case will never show - the number will always be greater than 1. The plural form was used only for other languages that special-case more than just "1".
Assignee | ||
Comment 19•14 years ago
|
||
Turned out test_AddonRepository.js was expecting extensions.getAddons.search.browserURL to not exist - and that in turn messed up various other parts of the test. Fix was just a simple switch of a boolean to tell it to expect it to exist. Carrying forward the r+, since that was such a trivial change.
Attachment #470365 -
Attachment is obsolete: true
Assignee | ||
Updated•14 years ago
|
Keywords: checkin-needed
Comment 20•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/164c156307c7
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: mozilla2.0b5 → mozilla2.0b6
Reporter | ||
Comment 21•14 years ago
|
||
So the number of search results we display in the search pane is still different from the results found on AMO. But that's another bug which is already on file and I cannot find right now. The link is displayed in builds on all platforms like Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20100922 Firefox/4.0b7pre
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 22•14 years ago
|
||
(In reply to comment #21) > But that's another bug which is > already on file and I cannot find right now. Bug 593332 ?
Reporter | ||
Comment 23•14 years ago
|
||
Could be. We will have to see.
You need to log in
before you can comment on or make changes to this bug.
Description
•