Closed
Bug 877506
Opened 12 years ago
Closed 12 years ago
[Buri][Shira-49405] USAT function Launch Browser is not working
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect, P1)
Tracking
(blocking-b2g:-)
RESOLVED
DUPLICATE
of bug 871402
blocking-b2g | - |
People
(Reporter: sync-1, Unassigned, NeedInfo)
Details
Attachments
(1 file)
8.45 KB,
application/x-zip-compressed
|
Details |
AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.111
Firefox os v1.0.1
Mozilla build ID:20130514070202
+++ This bug was initially created as a clone of Bug #459790 +++
Created an attachment (id=419611)
log
DEFECT DESCRIPTION:
[Shira-49405] USAT function Launch Browser is not working
REPRODUCING PROCEDURES:
USAT function Launch Browser is not working
EXPECTED BEHAVIOUR:
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
REPRODUCING RATE:
For FT PR, Please list reference mobile's behavior:
++++++++++ end of initial bug #459790 description ++++++++++
CONTACT INFO (Name,Phone number):
DEFECT DESCRIPTION:
REPRODUCING PROCEDURES:
EXPECTED BEHAVIOUR:
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
REPRODUCING RATE:
For FT PR, Please list reference mobile's behavior:
Comment 4•12 years ago
|
||
I did some test in v1.0.1 which worked as expected.
Can you retest with DEBUG traces on system app (icc_cache.js file DEBUG variable) and settings app (utils.js DEBUG variable) enabled in order to get the received JSON object?
Thanks in advance !
Flags: needinfo?(sync-1)
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Comment from Mozilla:I did some test in v1.0.1 which worked as expected.
Can you retest with DEBUG traces on system app (icc_cache.js file DEBUG variable) and settings app (utils.js DEBUG variable) enabled in order to get the received JSON object?
Thanks in advance !
Comment 9•12 years ago
|
||
triage with partner: this is not in the blocker list. tef-
blocking-b2g: tef? → -
Updated•11 years ago
|
Flags: needinfo?(sync-1)
You need to log in
before you can comment on or make changes to this bug.
Description
•