Closed
Bug 770755
Opened 12 years ago
Closed 12 years ago
Throw a warning when app name is too long for Gaia
Categories
(Marketplace Graveyard :: Validation, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
2012-07-05
People
(Reporter: cvan, Assigned: basta)
References
Details
We limit app names to 128 characters on Marketplace. And developers specify long names in their manifests so when users go to install the app and launch it from their B2G phones, the name gets truncated. If the "name" is longer than 9 characters (I think that's about the max), throw a warning telling them it will be truncated when natively installed.
Reporter | ||
Updated•12 years ago
|
Summary: Throw a warning when app name is too long → Throw a warning when app name is too long for Gaia
Assignee | ||
Comment 1•12 years ago
|
||
Done: https://github.com/mozilla/amo-validator/pull/167/files
Comment 2•12 years ago
|
||
Isn't this fixed? I saw this working on the marketplace prod just now doing a test.
Assignee | ||
Comment 3•12 years ago
|
||
Ah yes. Whoever closed the pull request didn't close the bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•12 years ago
|
||
See https://github.com/mozilla/amo-validator/pull/167/files#r1199160
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → mattbasta
Target Milestone: --- → 2012-07-05
Assignee | ||
Comment 5•12 years ago
|
||
Updated
Comment 6•11 years ago
|
||
The current checks, just look at the name attribute, not at the localized name... (Meta: Should I look at the app-validator or at the amo-validator repo?)
Assignee | ||
Comment 7•11 years ago
|
||
Here's the code that performs the check: https://github.com/mozilla/app-validator/blob/master/appvalidator/webapp.py#L38
Comment 8•11 years ago
|
||
So this code is just looking at name but not at the localized names. I wonder if it should iterate through all given in the locales dict and check the names in there too.
Assignee | ||
Comment 9•11 years ago
|
||
I've filed bug 870393 to fix that issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•