Closed Bug 414609 Opened 17 years ago Closed 17 years ago

Display appropriate message when there are no compatible search results

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.9beta3

People

(Reporter: mossop, Assigned: mossop)

References

Details

(Keywords: late-l10n)

Attachments

(1 file, 1 obsolete file)

When there are results returned from a search but none of them are compatible or not installed then we should display a message appropriately.
Assignee: nobody → dtownsend
Keywords: late-l10n
Blocks: 414449
Blocks: 414446
Blocks: 414447
Attached patch patch rev 1 (obsolete) (deleted) — Splinter Review
This adds an additional message when we find no compatible results from the search and tweaks some UI strings. Want to get this for b3.
Attachment #300150 - Flags: review?(robert.bugzilla)
Attached patch patch rev 2 (deleted) — Splinter Review
Rename the entities. Minor fix to the logic to only display the message when there are remote search results but none of them are compatible.
Attachment #300150 - Attachment is obsolete: true
Attachment #300154 - Flags: review?(robert.bugzilla)
Attachment #300150 - Flags: review?(robert.bugzilla)
Comment on attachment 300154 [details] [diff] [review] patch rev 2 r=me
Attachment #300154 - Flags: review?(robert.bugzilla) → review+
Comment on attachment 300154 [details] [diff] [review] patch rev 2 Approval for these string cleanups for b3
Attachment #300154 - Flags: approval1.9?
Comment on attachment 300154 [details] [diff] [review] patch rev 2 a=beltzner
Attachment #300154 - Flags: approval1.9? → approval1.9+
Checking in toolkit/locales/en-US/chrome/mozapps/extensions/extensions.dtd; /cvsroot/mozilla/toolkit/locales/en-US/chrome/mozapps/extensions/extensions.dtd,v <-- extensions.dtd new revision: 1.32; previous revision: 1.31 done Checking in toolkit/mozapps/extensions/content/extensions.css; /cvsroot/mozilla/toolkit/mozapps/extensions/content/extensions.css,v <-- extensions.css new revision: 1.19; previous revision: 1.18 done Checking in toolkit/mozapps/extensions/content/extensions.js; /cvsroot/mozilla/toolkit/mozapps/extensions/content/extensions.js,v <-- extensions.js new revision: 1.160; previous revision: 1.159 done Checking in toolkit/mozapps/extensions/content/extensions.xml; /cvsroot/mozilla/toolkit/mozapps/extensions/content/extensions.xml,v <-- extensions.xml new revision: 1.52; previous revision: 1.51 done Checking in toolkit/themes/gnomestripe/mozapps/extensions/extensions.css; /cvsroot/mozilla/toolkit/themes/gnomestripe/mozapps/extensions/extensions.css,v <-- extensions.css new revision: 1.5; previous revision: 1.4 done Checking in toolkit/themes/pinstripe/mozapps/extensions/extensions.css; /cvsroot/mozilla/toolkit/themes/pinstripe/mozapps/extensions/extensions.css,v <-- extensions.css new revision: 1.35; previous revision: 1.34 done Checking in toolkit/themes/winstripe/mozapps/extensions/extensions.css; /cvsroot/mozilla/toolkit/themes/winstripe/mozapps/extensions/extensions.css,v <-- extensions.css new revision: 1.39; previous revision: 1.38 done
Target Milestone: --- → Firefox 3 beta3
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: