Update:Remora Feedback: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(30 intermediate revisions by 12 users not shown)
Line 1: Line 1:
= Beta Feedback - http://preview.addons.mozilla.org =
= Beta Feedback - http://preview.addons.mozilla.org =
This page is for consolidation of the feedback on the new AMO Beta.  If you're more comfortable filing bugs, you're [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org&version=3.0 welcome to do that] instead.
This page is for consolidation of the feedback on the new AMO Beta.  If you're more comfortable filing bugs, you're [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org&version=3.2 welcome to do that] instead.
== xeen's comments ==
Developer Pages
* I do get an "An Error Occured" message when trying to update my extension's details. Even if it's just temporarily, adding reasons for failure would be nice.
* Numbers for download counts are unclear (Currently looks like "Downloads: 3287 / 92995".). Adding "(this week/total)" after the numbers or in the tooltip (or both) would surely help.
** has been fixed, although I don't know by whom
* When editing one of my addons I have two scrollbars - one for the iframe and one for the whole page. If I fullscreen on 1280x1024 everything's fine, but it gets worse if I resize Firefox.
* Although all of my extension releases were tagged "(public)" I was offered a "nominate for public" (or similar) link (probably import bug?). If there there is a difference between sandbox-public and real-public, then it's not clear to me and probably should be explained somewhere to (new) users.
* The interface should show nomination status always. I have a link to nominate if it hasn't been nominated but doesn't show any info if it's still being refused or declined.


== fligtar's comments ==
== Accessibility ==
Public Pages
* Changing text size results in bad layout. Ways to correct this: #otherAlso should specify min-width rather than width; class .addon has a background image of addon-tr.png - the vertical size of this image is not very big, so it quickly results in missing borders when text size is increased a fraction.
* http://remora.stage.mozilla.com/en-US/addons/versions/15004 three of those versions are STATUS_NULL which means they are incomplete and should not appear *anywhere* on the public side
* Unfortunately #otherAlso has been taken out of the flow and is absolutely positioned resulting in it overlapping other content at non-default text sizes.
* Sandbox should not have "We Recommend" section - should be renamed. Also, I just saw an add-on in that section with "This add-on is not available." surrounded by a red border - shouldn't be shown if it's not available.


Developer Pages
These sort of problems also tend to present themselves at higher DPI - have you tested at 120dpi?
* Small previews should not be resized to be larger
* Additem escapes fields with quotes sometimes
* Ability for public add-ons to go to sandbox if requested
* New feature implementation (not listing all here)


Misc
== SEO ==
* The application and platform shortnames are wrong. In the migrated dump, the shortnames are all equal to the regular names.
* The title "Firefox Addons" should be an H1, not an H2 so that search engines will pick it up. At the moment, the H1 is an image saying "mozilla" - not really something a search engine would find... Also, I'm not sure why font sizes and font colors are specified for that H1 given that it only contains an image.
* A meta description would give a search engine something to pull off the page.


== Archaeopteryx' comments ==
== Overflow ==
* The navigation bar contains too many text: The text gets wrapped and then it's getting ugly.
Even at normal font size, URLs in the body text of the addon description break out of the .addon class container. This looks bad. You could give the addon class a overflow:hidden but that's usually unsatisfactory. Gecko still doesn't implement text-overflow:ellipsis (bug #312156) or word-wrap (bug #99457) so the only other option is to inject <wbr> (or equivalent numeric entity) at alternate characters in long strings as chatzilla does.  
* For the first time a user logs into the sandbox, there should be a confirm box that he/she has read what the sandbox is (and there also should be no add-on on the page for this time).
--[[User:Rbirkby|Rbirkby]] 11:06, 15 February 2008 (PST)
* Only add-ons compatible with the user's Firefox and OS should be offered (saw Smoke, but no version for Win)
* Please don't waste so many space, starting the text in the add-on lists so much on the right. I would prefer starting it directly below the add-on title.
** At least make the space to the left equal. Currently the description seems to have a random left-marign --[[User:Xeen|xeen]]
* Search box in sandbox should also reviewed add-ons.
* Sandbox add-ons are shown in the developer page of public pages (redirected to not found).
* Probably, most developers will still ask for review for their add-on(s) because this will stay the only way for (anonymous) users to install an add-on without adding permission for add-on install from another server to their preferences.
* Maybe the min- and maxVersion for add-ons in the feed summary would be useful especially when new milestones are being released.
* German translation: "E-Mail" is the only correct version of this word.
** Fixed in trunk. Eigentlich weiß ich das: War wohl eher ein mehrfacher Tippfehler von mir... --[[User:Wenzel|wenzel]] 15:53, 5 February 2007 (PST)
---
* Link to Dev CP not yet localized (de-DE)
* Target application not detected (not shown during upload), categories for other applications should be hidden, allowed categories sorted by name
** Categories are now filtered by application and sorted alphabetically. As for the target app, I would need more specifics because it works for me. [[User:Fligtar|Fligtar]] 12:44, 9 February 2007 (PST)
*** [http://img119.imageshack.us/img119/9794/targetapplicationsnonelr9.png Target application: none] [[User:Archaeopteryx|Archaeopteryx]] 14:05, 11 February 2007 (PST)
* Step 3: Above first box, there are "Target application" and "Version notes" - something broken?
** Again, this looks fine for me, can you post a screenshot? [[User:Fligtar|Fligtar]] 12:44, 9 February 2007 (PST)
*** [http://img119.imageshack.us/img119/6797/targetapplicationsversiif8.png Screenshot] [[User:Archaeopteryx|Archaeopteryx]] 14:05, 11 February 2007 (PST)
* I am not a friend of localized add-on names.
* Link from the overview over my add-on to the author (me), gives a 404: [http://preview.addons.mozilla.org/de/users/47341]
** Fixed [[User:Fligtar|Fligtar]] 12:44, 9 February 2007 (PST)
* Add-on name too long for sidebar
* In Remora, I have to show the people my real name? Why? Why do I have to provide it?
* Add-ons in categories are sorted per page.
---
* During uploading an extension, the RSS item is already created after step one or two and the add-on name is missing. [http://img518.imageshack.us/img518/8541/extensionwithoutnamevz2.png Screenshot]
* Logging out redirects me to the login page. If the page isn't part of the dev CP, the page should not be changed, else the user should be redirected to the home page.
* It is currently not possible to save the preferred language. Log out, open a new tab and visit the preview, log in. It is always the useragent locale.
* Uploading a different add-on by another developer should only be possible if add-on name is different.
* de-DE home page: MicroHunter is called "Microjäger" here, but the "ä" is replaced by "?" - encoding problems?


== zeniko's comments ==
The "Other applications" control partially obscures "My account" and "Logout".


* Font size of the menu and the "Popular/New Extensions" list is awfully small. What about using 10pt or even 12pt as a minimal size for everything (except maybe the small print at the botton - although you'll want people to be able to read that as well).
== Reviews ==
* The main menu doesn't stick out at first glance. I'd actually expect it to be place more towards the top of the screen and have a more notable background. Suggestion: move the title image slightly to the right so the menu always starts at the same height right below the breadcrumbs.
It's rather unobvious that adding a rating/review for an extension requires you to be logged in. I'd highly recommend adding a one-line note above the submit button for not-logged in users saying something like "requires registration", or you'll risk pissing off would be commenters who don't want to go through the trouble of registering yet another account.
* On the extension pages as well as on the version history pages, the supported application versions should still be indicated so that you can see which releases actually apply to what you've got (important for non-browser applications).
* Hide the "See all preview images" link if there's only the one preview image shown anyway.
* If you right-click on "Install Now" and try to save the extension to disk, the file name defaults to "Install Now" because we're now downloading a directory and no longer a file. Please revert to adding a descriptive filename (e.g. extension_name-version-supported_apps.xpi).
* Please make sure that Console² is actually written that way everywhere - I've already [[http://preview.addons.mozilla.org/en-US/users/info/9225 spotted]] the first "Console& sup2;".
* Following the link to a sandboxed extension from an author's page results in a log-in form without any further explication.
* The fine print in the footer is even more difficult to read because there's no border between the last line and the bottom of the page.
* And what about changing "Recommended Add-ons" to "Recommended Extensions" unless we actually recommend themes or plug-ins as well?


== nasano's comments ==
== Firefox/OS Version ==
It seems that there is no simple way to specify the Firefox version and OS the extensions shown should be compatible with. Nor is this information shown anywhere in the lists. This results in the rather frustrating situation that one might have to browse through a long list of extensions only to detect when trying to install the extension that it is not compatible with your browser.
This problem gets even worse if somebody just wants to download an extension for a different browser (e.g. when an administrator running Linux prepares software and extensions for a Windows installation).


* I can't login to AMO preview site. I registered my account, but I coudn't get an e-mail to confirm. So I used Password Reset, but AMO send me noting. My e-mail address is asano [at] po [dot] jah [dot] ne [dot] jp.
Especially for the launch of Firefox 3.0 this will be important as otherwise people will have too much difficulty in finding FF3.0 enabled extensions/themes.
** Sorry -- this was a problem recently fixed in trunk. Once the next update to the preview is published, you'll be able to have the email resent, and you'll also be able to login correctly after clicking the link in the email. --[[User:Wenzel|wenzel]] 13:16, 8 February 2007 (PST)
*** Is this fixed now? I can't login yet. Please see [https://bugzilla.mozilla.org/show_bug.cgi?id=369715 bug 369715].


== gekacheka's comments ==
== Advanced search ==
There should be some form that allows a more advanced search, especially the specification of a FF version and/or OS that the addon must be compatible with. Other advanced search features should be an option to exclude or include "experimental" addons or limit the extensions to those of specific authors.


<dl>
== Usability / UI revisions ==
<dt>Separating Add-ons by Application</dt>
* People who are used to the term "themes" (existing users) are having difficulty finding them in the current hierarchy.
<dd>What are plans for separating add-ons by application (for applications besides Firefox)?  The current (non-preview) AMO supports
** Potential solution: Finish changing the name of the category from "Interface Customizations" to "Themes & Appearance"
* https://addons.mozilla.org/thunderbird/ Thunderbird
* There's inconsistency between what down-arrows mean on menu headers (there's a drop-down menu available here) vs. what they mean on "Add to Firefox" buttons (up for debate! "down"load?)
* https://addons.mozilla.org/seamonkey/ Seamonkey
** Potential solution: remove the down arrow from the "Add to Firefox" buttons. The arrow doesn't really have much useful semantic meaning -- it doesn't really convey "add to firefox" -- so it's really just clutter.
* https://addons.mozilla.org/sunbird/ Sunbird
* The issue of not knowing whether a given add-on is compatible with your version of Firefox/other application is a big deal
However, it looks like the current preview of Remora removes this support (links on home page, application pages, search by application, application in add-on URL for download referrer). ([[User:Gekacheka|Gekacheka]] 07:49, 10 February 2007 (PST))<br>
* Listing stuff from the sandbox (experimental) by default is not useful, since even if the person goes to the trouble of creating an account in order to access it there is no useful status information such as when it was created, how long its been in a queue or what version it is compatible with. Why not only list experimental add-ons if the person is logged in?
Related bugs:  
* Clicking on a category button such as "security and privacy" for Thunderbird add-ons gives three add-ons, in vertical columns. This is hard to read, and unexpected. Its also hard to browse all of the entries for this category since thats not one of the choices in the "see all privacy and security" box. Whats wrong with alphabetical sorting as a choice? If nothing else sometimes a user has a rough idea of the name and wants to try to find it via browsing rather than searching.
*{{Bug|367574}} Ability to filter search of an Add-ons by application
* If the user is navigating add-ons or themes for a specific application only add-ons and themes for that application should be shown. For example, in the Thunderbird add-ons privacy and security category the first page shows the Hip Hop Radio Extension for Firefox. Thats experimental and Firefox specific.
*{{Bug|369194}} Track add-on download counts per application (most popular...)
* If I search for the Lightning extension while running Firefox under Linux it has a "Download Now (Windows)" button for that extension. This is confusing as all of the other add-ons have "Download Now" and it choose the wrong platform when it tried to be helpful. If I click on the entry it shows separate download links for each platform. However, if I look at some other extension such as ltnPlus it uses "Download Now" both in the summary and when I click on the entry. Behavior needs to be more consistent and predictable.
</dd>
* There should be more consistency in categories among the different products. Firefox has interface customizations and toolbars, which are generic enough they would be useful in Thunderbird and probably other applications. Firefox has "other" while Thunderbird has "miscellaneous", whats the difference? Firefox has "photos, music and media" while SeaMonkey has "photos and media", why are they different?
</dl>
*  Looking at the number of categories (14 for firefox, 11 for SeaMonkey, 6 for Thunderbird, 3 for sunbird) one gets the impression some applications are not first class citizens. You would expect SeaMonkey to have the same categories (or more since its really a superset) as Firefox. Obvious categories such as Spam are missing for Thunderbird and SeaMonkey.
* Other web sites (for example Amazon) adapt recommendations for the user, and let you provide feedback to tailor the recommendations. If I look at the Firefox recommendations the first item is Zotero, something for automatic capture of citation information from web pages. Thats not exactly mainstream :) It has 5 reviews and 13,126 downloads, which doesn't sound like much. Its not one of the "featured" add-ons. Its not obvious why it was chosen, or that its tailored for me.
* There isn't any information to help deal with abandoned add-ons. For example, Frank DiLecce has written a lot of popular extensions. His web site is long gone, he is no longer using the mozillaZine forums, he hasn't updated his extensions for years, and nobody has been able to contact him for years. Its not clear whats the legal status of his extensions, which prevents anybody from taking over their maintenance.
*Searching for Noia (for the Noia themes) returns three entries. Two of them have identical names - Noia 2.0 eXtreme. You have to click on each entry to see that one is version 2.36 and one is version 3.0. That information should have been shown on the entry (the summary).
* Many add-ons require the user to figure out how to bypass the version check. If the add-on causes problems they sometimes need to use safe mode to let them access the menu to disable or uninstall the add-on. This information isn't available in the applications help. It would help if the web site provided some generic installation help for add-ons, even if all they did was provide links to a few SUMO and mozillaZine KB articles.
* The web page for Foxmarks Bookmark Synchronizer 2.0.43 displays three images (under "More Images") as three vertical lines. If you try to display any of them you get an error message about it can not be displayed because it contains errors.
* The date of release for addons and themes should be visible when browsing.


 
== Search Results Page ==
= Alpha Feedback =
The SRP should support sorting and filtering of the search results, similar to the sorting options already available on the "browse extension by category" page. Filtering can filter results by specific product/version/locale ...
See the [http://blog.mozilla.com/webdev/2007/01/02/amo-3.0-alpha-public-preview/ announcement] on the Mozilla webdev blog.
See bug 401136[https://bugzilla.mozilla.org/show_bug.cgi?id=401136] for details.
 
The feedback (bugs, suggestions) that we fixed/dealt with were moved to a [[Update:Remora Feedback/Alpha Feedback Fixed|reference page]].
 
== fligtar's comments ==
I like the overall look, but I have a few comments about certain aspects:
* The discussion header/footer is noticeably different.
* Discussions show a CakePHP favicon for me
 
== clouserw's comments ==
* Old URLs should redirect into the new format so we don't get 404s ([https://bugzilla.mozilla.org/show_bug.cgi?id=362526 bug 362526])
* Pages should validate
* Discussions can be started that aren't related to an addon (just click "discussions" in the header, then start a new topic)
* You can (sorta, temporarily) disable someone's account:
** Go to the [http://preview.addons.mozilla.org/en-US/users/pwreset password reset] page and enter someone's email address
** They'll get an email saying someone requested a reset, and to ignore it if it wasn't them, however, a confirmationcode has been added to the database for them
** If they try to login, it will tell them to confirm the account and kick them to the front page
* NSA would like the last name field to not be required
* /addons/ should go somewhere
* the link to MDC is hardcoded to english. ([http://blog.mozilla.com/webdev/2007/02/02/amo-preview-updates-3/#comment-223 from blog])
* The warning on the [http://remora.stage.mozilla.com/en-US/addons/versions/398 previous versions] page needs to be more prominent
* When in the sandbox, clicking a link in the breadcrumbs kicks you back out to the public side
* I don't think the red box around sandbox add-on's install links is effective.  At the least, we should provide a tooltip to explain it.  Maybe we could talk to the designers and get a pretty red button or something?
* When selecting dynamic translations, if LANG=en-US, we shouldn't select the fallback and the language - it's just twice the joins with no value
 
== wenzel's comments ==
* Search algorithm is improvable: The binary matching creates many hits with the same score in spite of their obviously different relevance.
* "find similar add-ons" sometimes shows different categories with the same name?  ([http://preview.addons.mozilla.org/en-US/addons/display/398 example])
 
== dria's comments ==
* Seems to be a bug at [http://preview.addons.mozilla.org/en-US/discussions/post.php?AddOnID=398] when not logged in.  At very least there should be a significantly friendlier message suggesting the user log in :)
 
== Dao's comments ==
* I don't see how the user is expected to find, say, Thunderbird extensions. AMO2 was too Firefox-centric, AMO3 seems even worse. http://www.erweiterungen.de/ does this better.
** answer from cameleon: I fill the [https://bugzilla.mozilla.org/show_bug.cgi?id=367574 Bug 367574] – Ability to filter search of an Add-ons by application (Firefox or Thunderbird) on bugzilla about this problem.
 
== DonGato's comments ==
* Doesn't the discussion header look bad? I think a right and left border is needed.
 
== pascalc's comments ==
* on the right sidebar menu, the "Build your own" link should point to the localized version of the documentation (http://developer.mozilla.org/{locale}/docs/Extensions) if it exists
** I agree. But I wonder how we can find out if it exists, before making the link. --[[User:Wenzel|wenzel]] 10:24, 16 January 2007 (PST)
** The Extension part of the link is usually translated. So, there is no way how to do this automatically. I would go with <code>'http://developer.mozilla.org' . _('sidebar_navlink_build_your_own_href')</code> The same issue is with [http://developer.mozilla.org/en/docs/Creating_OpenSearch_plugins_for_Firefox Creating_OpenSearch_plugins_for_Firefox] at  search engines page. --[[User:Pawell|Pawell]] 21 January 2007
* Website ignores Thunderbird, the front page should at least say "Add-ons extend Firefox and Thunderbird..." and not only Firefox
** Thank you. Multi-app support is definitely planned however not yet supported in the alpha version. --[[User:Wenzel|wenzel]] 19:50, 18 January 2007 (PST)
 
== RenegadeX's comments ==
It's hard to test the Preview site properly with the limited # of addons currently added, but I 2nd everything already said on this page. Have you guys learnt nothing over 3+ revisions of AMO? Users are tearing out their hair crying, "All I want to do is find a specific addon or browse the mass of addons quickly and easily" - and yet with each AMO revision, it continues to be a frustrating experience:
* On an [http://preview.addons.mozilla.org/en-US/addons/display/138 Extension(or Theme)'s page], you have the Extension Name followed by Version# on the same line (good to see it back, thanks - v2 was not good). Further down the page you have Version# and timestamp, which is thus partially redundant & a waste of space. Suggestion: go back to something closer to v1's implementation ([http://img222.imageshack.us/img222/9222/amoextensionspage2oldlo0.jpg screenshot]) which put it all at the top. Clean it up a little by putting the 'released on..' on its own line.
* Ditto the above - move it up, on the other listing pages (such as [http://preview.addons.mozilla.org/en-US/addons/recommended/ Recommended Add-ons]).
 
'' I could easily go on with my list but this is getting depressing. This thing was meant to be an improvement, was it not? Come on, this shouldn't be this difficult!'''
[[User:RenegadeX|RenegadeX]] 04:26, 17 January 2007 (PST)
* Thank you for your extensive feedback. That helps us a lot to make Remora better. Regarding your "improvement" question: Keep in mind that the current public preview is still an "alpha" version. It is, almost by definition, incomplete, sometimes buggy, has rough edges and is far away from perfect -- or from its final state, for that matter. Therefore it is important that you tell us what you like, and what you don't, so you can influence how Remora will look and feel like when it's done. --[[User:Wenzel|wenzel]] 11:19, 17 January 2007 (PST)
 
== Yoko's comments ==
* The plugins must be selected by UA of browser (linux's users not see the Windows plugins) as for the official Firefox web page.
* The thunderbird's and nvu's extensions are not very easy to find.
* I think that it's will good to multiply the section of extension. By exemple the developer tools's extensions can to be split in "PHP extension", "javascript extension", "webmaster extension", etc
 
== Moe's comments (from [http://blog.mozilla.com/webdev/2007/01/18/amo-preview-updates-2/#comment-27 blog]) ==
* No separation between products. What if I’m only interested in Thunderbird?
 
== Dolske's comments ==
 
Overall it's looking good! Here are my comments:
 
* Adblock got featured on the front page for one page load, but the preview image just says "1145".
 
* The little orange arrow in the green "install now" link looks too much like a UI element, implying a dropdown menu there.
 
* "Mozilla is providing links to these applications as a courtesy, and makes no representations regarding the applications or any information related there to." Given the legalese disclaimer, is "We Recommend" ok to say? The disclaimer in the footer also seems to be forced to 3 centered lines. Can this be flowed like normal text, non-centered, so it doesn't take up so much space?
** I reduced the margin so that looks a little better there! --[[User:Wenzel|wenzel]] 16:32, 2 February 2007 (PST)
 
* The [http://preview.addons.mozilla.org/en-US/addons/browse Browse] page linked from the right-hand navigation bar seems awkward. It only lists extensions and themes; no dictionaries, plugins, or search engines. But still, "Browse" seems a misfitting title for this page, since I'm not able to browse anything. Maybe "Other Addons" or "More Addons", since it's in proximity to "Recommended Addons"?
 
* Can "Recommended Addons" be things other than extensions? If so, things at this level should be identified as to why type of addon they are.
 
* The "Search Engines" page is inconsistent with the other top-level addon-type pages (should be a list of categories). Will Remora be incorporating the Mycroft content?
 
* Plugins... Oh boy. Entries should look like other addons (formatting, download button, etc.). Can we do OS detection here (like extensions?) and provide a single appropriate link? The links to plugindoc.mozdev.org should go elsewhere (wiki.m.o?). Mozdev isn't the right place for this kind of content. It might be worth considering giving each plugin its own page, and have the top-level plugins page list them (in a format similar to the categories on other top-level addon-type pages). Not to be a Suite hater, but the Mozilla Suite doesn't need to be mentioned here.
 
* s/Add a review/Add your review/? If there are no reviews, be a little more verbose, eg "No reviews for this addon -- add your review". (Doing this on a single line avoids a bunch of white space for unreviewed addons).
 
* Ditto the above for comments. The difference between comments and discussions isn't very clear. A better format might be (ignore Wiki's whitespace):
 
:::: '''Discussions'''
::::<u>This thing is awesome</u>
::::(2 replies, last by SomeGuy on December 3rd)
:
::::<u>This thing sucks</u>
::::(no replies, posted by SomeGal on January 4th)
:
::::<u>View all</u> (14 topics)
::::<u>Add a new topic</u>  &lt;--- remove this link?
 
* If no discussions exist for an addon, don't show "See all discussions (0)". Just make it a single link (ala my previous reviews comment)
 
* When viewing discussions, there should be a note that you need to log in to add a new comment/topic.
 
* Add a pony.
** I second that. --[[User:Wenzel|wenzel]] 14:22, 30 January 2007 (PST)
 
* Nice effect with the animation to show a review's content, but that makes it inconsistent with clicking on a discussion topic (which doesn't animate to show the topic's body, but takes you to a new page). The review text should just be shown by default (subject not linkified for animation), probably trimmed (with an appended "more" link that animates to show the rest?) so that long reviews don't take up more than a few lines by default.
 
Hmm, I guess that's enough comments for now! :-)
 
== Pawell's l10n comments ==
* Links to MDC should point to corresponding localization (see Pascal's comment)
* The 'Home' link should point to {locale}.www.mozilla.com/{locale}/
 
* The construction of 'Browse all {addon-type}' can't be properly translated in languages with different genders and pronoun inflection
::::Example:
::::::Browse all Extensions -> Procházet všechn'''a''' rozšíření
::::::Browse all Themes    -> Procházet všechn'''y''' motivy vzhledu
 
Moreover, we need to use the lowercase for the {addon-type} string in the middle of the sentence.
 
*  The same holds for 'Popular {addon-type}'
::::Popular Extension -> Oblíben'''á''' rozšíření
::::Popular Themes    -> Oblíben'''é''' motivy vzhledu
 
Thanks for your comments, Pawell.  These are very relevant, and unfortunately, the tools
we're using don't provide a way to handle declinations programmatically.  For
translating the examples you've provided, we're going to have to rely on
localizers interpreting the context, and if necessary, leaving out the pronouns.
For example, instead of "Browse all Extensions" it would be translated as
"Browse Extensions".  We could add comments in the .po file to help recognize
the areas where this could come up.  Any thoughts on this? --clouserw
 
== Juan's comments ==
* Show the extension image while browsing. The image conveys a lot of information. Having to click on the + sign to see it is not good enough. Use a thumbnail if the provided image is too big.
* It is nice to have the search box at the top. But it is hard to find. It looks part of the Mozilla site chrome. Give it a more prominent position.
* Too much white space.
* A *lot* depends on how "relevance" is determined when sorting the extensions.
[Jan 30 2007]
 
== Archaeopteryx' comments ==
* Nickname is now surname, so you made me Mr Archaeopteryx
* Add possibility to undo expand information in list view ("No, this isn't something for me")
* Add a list of application categories (only add-ons for application A and so on) under the current navigation at the left (with icon would be good)
* Reduce the height of the header on the (trunk) home page - you have to scroll to see the recommended add-on name on a notebook
* Add expand/reduce function to developer page (user info)
* Link to top of discussions page reloads page because http instead of https used ([https://remora.stage.mozilla.com/de/discussions/?AddOnID=7 example])
* [http://preview.addons.mozilla.org/de/discussions/post.php?AddOnID=138 New discussion page]: Drop down too small (because only one choice) and forum title string not yet translated
* If plugin list gets filtered by used OS, add the possibility to show all (for downloading possibility).
* "Adobe" vs. "Adobe Systems" on plugins page
* Maybe add the two ([https://addons.mozilla.org/firefox/3682/ 1], [https://addons.mozilla.org/firefox/3698/ 2]) extensions which are able to convert input fields to search engines to the search engines home page - it's faster than writing the search plugin on his own.
 
== dikrib's comments ==
Example: http://preview.addons.mozilla.org/en-US/addons/browse/type:1/cat:4
* Url could be prettier, like http://preview.addons.mozilla.org/en-US/addons/extensions/devtools
* The element "Browse" in breadcrumbs should be leaved out
* Last element in breadcrumbs should not be linkifyed.
* When you click the + you cannot go back. There should be a -
* The +/- makes no sense unless there is a difference in size for the two views. Why should I have to click the + to see a screenshot instead of a blank space? The idea of folding the items is great, but when they are folded, they should take up much less space. Two lines max.
* Include links Fold all/Unfold all.
 
* Discussions section seems to need a little care to make it melt into the rest of the side.
* When trying to log in, I get a white screen with the text "Please confirm your account". It disappears quickly. Please make it prettier and maybe put a link "resend confirmation mail"
* Sending confirmation mails for creating new accounts does not work.
 
I miss some l10n docs.
* Will it be possible to change the list of recommended addons?
* Will the search engine list be a full list like mycroft or a recommended list like on current AMO? If it is a recommended list, it should be localizable. The list at AMO right now is somewhat US centric.
* How is translation of addon descriptions going to work? Please make sure it is possible to integrate it with localizing the addon itself. Maybe integrate it into babelzilla.

Latest revision as of 01:57, 22 April 2008

Beta Feedback - http://preview.addons.mozilla.org

This page is for consolidation of the feedback on the new AMO Beta. If you're more comfortable filing bugs, you're welcome to do that instead.

Accessibility

  • Changing text size results in bad layout. Ways to correct this: #otherAlso should specify min-width rather than width; class .addon has a background image of addon-tr.png - the vertical size of this image is not very big, so it quickly results in missing borders when text size is increased a fraction.
  • Unfortunately #otherAlso has been taken out of the flow and is absolutely positioned resulting in it overlapping other content at non-default text sizes.

These sort of problems also tend to present themselves at higher DPI - have you tested at 120dpi?

SEO

  • The title "Firefox Addons" should be an H1, not an H2 so that search engines will pick it up. At the moment, the H1 is an image saying "mozilla" - not really something a search engine would find... Also, I'm not sure why font sizes and font colors are specified for that H1 given that it only contains an image.
  • A meta description would give a search engine something to pull off the page.

Overflow

Even at normal font size, URLs in the body text of the addon description break out of the .addon class container. This looks bad. You could give the addon class a overflow:hidden but that's usually unsatisfactory. Gecko still doesn't implement text-overflow:ellipsis (bug #312156) or word-wrap (bug #99457) so the only other option is to inject (or equivalent numeric entity) at alternate characters in long strings as chatzilla does. --Rbirkby 11:06, 15 February 2008 (PST)

The "Other applications" control partially obscures "My account" and "Logout".

Reviews

It's rather unobvious that adding a rating/review for an extension requires you to be logged in. I'd highly recommend adding a one-line note above the submit button for not-logged in users saying something like "requires registration", or you'll risk pissing off would be commenters who don't want to go through the trouble of registering yet another account.

Firefox/OS Version

It seems that there is no simple way to specify the Firefox version and OS the extensions shown should be compatible with. Nor is this information shown anywhere in the lists. This results in the rather frustrating situation that one might have to browse through a long list of extensions only to detect when trying to install the extension that it is not compatible with your browser. This problem gets even worse if somebody just wants to download an extension for a different browser (e.g. when an administrator running Linux prepares software and extensions for a Windows installation).

Especially for the launch of Firefox 3.0 this will be important as otherwise people will have too much difficulty in finding FF3.0 enabled extensions/themes.

Advanced search

There should be some form that allows a more advanced search, especially the specification of a FF version and/or OS that the addon must be compatible with. Other advanced search features should be an option to exclude or include "experimental" addons or limit the extensions to those of specific authors.

Usability / UI revisions

  • People who are used to the term "themes" (existing users) are having difficulty finding them in the current hierarchy.
    • Potential solution: Finish changing the name of the category from "Interface Customizations" to "Themes & Appearance"
  • There's inconsistency between what down-arrows mean on menu headers (there's a drop-down menu available here) vs. what they mean on "Add to Firefox" buttons (up for debate! "down"load?)
    • Potential solution: remove the down arrow from the "Add to Firefox" buttons. The arrow doesn't really have much useful semantic meaning -- it doesn't really convey "add to firefox" -- so it's really just clutter.
  • The issue of not knowing whether a given add-on is compatible with your version of Firefox/other application is a big deal
  • Listing stuff from the sandbox (experimental) by default is not useful, since even if the person goes to the trouble of creating an account in order to access it there is no useful status information such as when it was created, how long its been in a queue or what version it is compatible with. Why not only list experimental add-ons if the person is logged in?
  • Clicking on a category button such as "security and privacy" for Thunderbird add-ons gives three add-ons, in vertical columns. This is hard to read, and unexpected. Its also hard to browse all of the entries for this category since thats not one of the choices in the "see all privacy and security" box. Whats wrong with alphabetical sorting as a choice? If nothing else sometimes a user has a rough idea of the name and wants to try to find it via browsing rather than searching.
  • If the user is navigating add-ons or themes for a specific application only add-ons and themes for that application should be shown. For example, in the Thunderbird add-ons privacy and security category the first page shows the Hip Hop Radio Extension for Firefox. Thats experimental and Firefox specific.
  • If I search for the Lightning extension while running Firefox under Linux it has a "Download Now (Windows)" button for that extension. This is confusing as all of the other add-ons have "Download Now" and it choose the wrong platform when it tried to be helpful. If I click on the entry it shows separate download links for each platform. However, if I look at some other extension such as ltnPlus it uses "Download Now" both in the summary and when I click on the entry. Behavior needs to be more consistent and predictable.
  • There should be more consistency in categories among the different products. Firefox has interface customizations and toolbars, which are generic enough they would be useful in Thunderbird and probably other applications. Firefox has "other" while Thunderbird has "miscellaneous", whats the difference? Firefox has "photos, music and media" while SeaMonkey has "photos and media", why are they different?
  • Looking at the number of categories (14 for firefox, 11 for SeaMonkey, 6 for Thunderbird, 3 for sunbird) one gets the impression some applications are not first class citizens. You would expect SeaMonkey to have the same categories (or more since its really a superset) as Firefox. Obvious categories such as Spam are missing for Thunderbird and SeaMonkey.
  • Other web sites (for example Amazon) adapt recommendations for the user, and let you provide feedback to tailor the recommendations. If I look at the Firefox recommendations the first item is Zotero, something for automatic capture of citation information from web pages. Thats not exactly mainstream :) It has 5 reviews and 13,126 downloads, which doesn't sound like much. Its not one of the "featured" add-ons. Its not obvious why it was chosen, or that its tailored for me.
  • There isn't any information to help deal with abandoned add-ons. For example, Frank DiLecce has written a lot of popular extensions. His web site is long gone, he is no longer using the mozillaZine forums, he hasn't updated his extensions for years, and nobody has been able to contact him for years. Its not clear whats the legal status of his extensions, which prevents anybody from taking over their maintenance.
  • Searching for Noia (for the Noia themes) returns three entries. Two of them have identical names - Noia 2.0 eXtreme. You have to click on each entry to see that one is version 2.36 and one is version 3.0. That information should have been shown on the entry (the summary).
  • Many add-ons require the user to figure out how to bypass the version check. If the add-on causes problems they sometimes need to use safe mode to let them access the menu to disable or uninstall the add-on. This information isn't available in the applications help. It would help if the web site provided some generic installation help for add-ons, even if all they did was provide links to a few SUMO and mozillaZine KB articles.
  • The web page for Foxmarks Bookmark Synchronizer 2.0.43 displays three images (under "More Images") as three vertical lines. If you try to display any of them you get an error message about it can not be displayed because it contains errors.
  • The date of release for addons and themes should be visible when browsing.

Search Results Page

The SRP should support sorting and filtering of the search results, similar to the sorting options already available on the "browse extension by category" page. Filtering can filter results by specific product/version/locale ... See bug 401136[1] for details.

Retrieved from "https://wiki.allizom.org/index.php?title=Update:Remora_Feedback&oldid=91032"