Closed
Bug 738298
Opened 12 years ago
Closed 12 years ago
navigator.mozApps.mgmt.getAll() doesn't handle non-ASCII characters in the manifest
Categories
(Core Graveyard :: DOM: Apps, defect)
Core Graveyard
DOM: Apps
Tracking
(blocking-kilimanjaro:+, blocking-basecamp:+)
VERIFIED
FIXED
mozilla17
People
(Reporter: djf, Assigned: fabrice)
References
Details
(Whiteboard: [qa!])
Attachments
(1 file)
1.15 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
When I use navigator.mozApps.mgmt.getAll() in the Gaia homescreen, and set the local to French, accented characters in the app name are garbled. It appears that UTF-8 strings in the manifest are being treated as 7-bit ASCII and not properly converted into JavaScript UTF-16 strings.
Assignee | ||
Updated•12 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Comment 1•12 years ago
|
||
As a point of similarity, this issue also occurs with desktop native installation (see bug 733482). Seeing that this happens in more than spot makes me think that this UTF-8 character issue could be more areas we have not looked at yet.
Comment 2•12 years ago
|
||
We should definitely include some non-ASCII manifests in our testing (right now all our test manifests are strictly ASCII).
Comment 3•12 years ago
|
||
Hey jason I had written a manual test with japanese characters. In the interim, could you add this test to your smoketest. https://github.com/mozilla/openwebapps/tree/develop/site/tests/apps/app3
Comment 4•12 years ago
|
||
To do that you need to run the node test server, and load appstore.html the above app will be listed to be installed, and you should be able to install to the dashboard, view on dashboard..etc
Comment 5•12 years ago
|
||
Yup, I've added the UTF-8 character test on native install here on test case IA-15 (https://docs.google.com/spreadsheet/ccc?key=0AiZoGR-iOAlUdDdfMHo5aTI2WjVIeWxnNWxvV0ZVOWc#gid=0).
Comment 6•12 years ago
|
||
I you post the manifest somewhere I can add it to the /appdir/ list
Comment 7•12 years ago
|
||
ian that touches on another issue which is where / how to host test apps ...... I think the staging server would be a good spot for this, the question is whether we can get ops to open some firewall ports so we can run the node.js test server. i think that would be optimal
Comment 8•12 years ago
|
||
I think appengine or heroku might be better hosting options for samples.
Comment 9•12 years ago
|
||
Filed bug 738845 for the hosting of test apps. Let's pull the conversation on the test case applications over to that bug.
Comment 10•12 years ago
|
||
Jason, do you have an eta on this bug fix ?
Comment 11•12 years ago
|
||
Which bug are you referring to? This one? Bug 738845? If it's bug 738845, please comment in that bug.
Comment 12•12 years ago
|
||
I was referring to this bug.
Comment 13•12 years ago
|
||
This is an implementation bug - I'm not the appropriate person to fix this bug.
Comment 14•12 years ago
|
||
k, wanted to determine if you had more information about the bug than I did... Fabrice: do you have an eta on this bug fix ?
Assignee | ||
Comment 15•12 years ago
|
||
I'll probably have a fix by the end of next week
Updated•12 years ago
|
Assignee: fabrice → nobody
Component: General → DOM: Mozilla Extensions
Product: Web Apps → Core
QA Contact: general → general
Whiteboard: [mozappsapi]
Updated•12 years ago
|
Whiteboard: [mozappsapi] → [mozApps API 1.0]
Updated•12 years ago
|
Whiteboard: [mozApps API 1.0] → [mozApps API 1.0] [marketplace-beta?]
Updated•12 years ago
|
Whiteboard: [mozApps API 1.0] [marketplace-beta?] → [mozApps API 1.0]
Updated•12 years ago
|
Whiteboard: [mozApps API 1.0]
Comment 16•12 years ago
|
||
Nominating for k9o - this affects localized b2g apps
blocking-kilimanjaro: --- → ?
Updated•12 years ago
|
blocking-kilimanjaro: ? → +
Updated•12 years ago
|
blocking-basecamp: --- → ?
Updated•12 years ago
|
blocking-basecamp: ? → +
Updated•12 years ago
|
Assignee: nobody → fabrice
Assignee | ||
Comment 17•12 years ago
|
||
Tested by changing some manifest.webapp files in gaia to use utf-8 instead of the current escaping.
Attachment #647477 -
Flags: review?(21)
Comment 18•12 years ago
|
||
Comment on attachment 647477 [details] [diff] [review] patch Review of attachment 647477 [details] [diff] [review]: ----------------------------------------------------------------- \o/
Attachment #647477 -
Flags: review?(21) → review+
Assignee | ||
Comment 19•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/2bef20dfc8fb
Updated•12 years ago
|
QA Contact: jsmith
Whiteboard: [qa+]
Comment 20•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/2bef20dfc8fb
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Comment 21•12 years ago
|
||
Testing on desktop, this looks okay outside of the regression that was caught on Android. I'll want to test this on Firefox OS though to be sure.
Assignee | ||
Comment 22•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #21) > Testing on desktop, this looks okay outside of the regression that was > caught on Android. I'll want to test this on Firefox OS though to be sure. Which android regression?
Comment 23•12 years ago
|
||
(In reply to Fabrice Desré [:fabrice] from comment #22) > (In reply to Jason Smith [:jsmith] from comment #21) > > Testing on desktop, this looks okay outside of the regression that was > > caught on Android. I'll want to test this on Firefox OS though to be sure. > > Which android regression? bug 779490
Comment 24•12 years ago
|
||
Verified on 8/6/2012 Firefox OS Daily Build with Ed Lee's app with Japanese characters.
Status: RESOLVED → VERIFIED
Whiteboard: [qa+] → [qa!]
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•