Closed Bug 397376 Opened 17 years ago Closed 17 years ago

The extension dual description? (first in italics and truncated)

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: starofsouth, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070805 Firefox/2.0.0.6 (Swiftfox) Build Identifier: What's the purpose of the dual descriptions? It's fairly annoying. "This extension pops up an alert dialog to warn chrome and extension developers about one particular type of leak. It warns when chrome windows close but leave other code pointing at their JavaScript... This extension pops up an alert dialog to warn chrome and extension developers about one particular type of leak. It warns when chrome windows close but leave other code pointing at their JavaScript objects." We see this silliness on most extension pages. I guess the addon author should add a short description but they don't seem to... Anyways, this needs to be addressed somehow. Thanks bye! Reproducible: Sometimes
The reason for this was the old AMO v2, now we have AMO v3. v2 had no brief description, so the first xx characters from the description were taken as summary and will exist as it as long as the developer doesn't update it. So it will probably be a WONTFIX.
Where is this short description used? Does it have to appear on the "home page" of an extension? I think it's a bit silly to expect the authors to fix basically amo bugs.
The summaries are used on search results pages and category listing for example. And yes, displaying them both makes sense if the author actually makes use of them: Then the summary will give you a one-sentence description of what the add-on does, and the description paragraph will give you a more in-depth idea of its capabilities.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.