Closed Bug 703716 Opened 13 years ago Closed 6 years ago

describe whitespace meaning in description and name

Categories

(Core Graveyard :: DOM: Apps, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ianbicking, Unassigned)

Details

From: https://github.com/mozilla/openwebapps/issues/6

Right now the description is just "human readable", but there's no indication about how newlines or multiple spaces should be handled.

I recommend:

    The name is a single-line, and all whitespace is normalized to one space (i.e., newlines are equivalent to a space).
    The description can contain newlines and whitespace, and both are preserved when displayed. That means in the HTML case that newlines are replaced with <br> and multiple spaces use &nbsp;. This allows, for example, simple indented lists.

---

from Lloyd:

I like your proposal for name, but think we should do the same for description. My thinking is that if you support overly simple markup, you constrain the display of information without providing any real expressive power. I think we should say description is a chunk of unbroken prose, and in doing so we give a lil' bit more structure and freedom to the folks designing the UA integration.

just a hunch.

---

from Ian:

Android apps, from what I can tell, have a screenshot and a plaintext description. The description is frequently more than one paragraph, and includes bullet points. This seems reasonable to me.
Priority: -- → P2
Is this a mozapps api bug? If so, migrate this bug to Core --> DOM/Mozilla Extensions.
It's a matter of specification; the mozApps API doesn't actually do anything with the description, but the marketplace and dashboard do, and neither has guidance on how to interpret whitespace in the description.
Component: General → DOM: Apps
Priority: P2 → --
Product: Web Apps → Core
Product: Core → Core Graveyard
Core Graveyard / DOM: Apps is inactive. Closing all bugs in this component.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.