Closed
Bug 893766
Opened 11 years ago
Closed 11 years ago
SMS Web Activity call from 3rd party web apps wont transfer phone number
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Firefox OS Graveyard
Gaia::SMS
Tracking
(blocking-b2g:leo+)
People
(Reporter: zoltanf, Assigned: rik)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
235.75 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36
Steps to reproduce:
Run this example code in Gaia, in a 3dt party packaged web app:
var sms = new MozActivity({
name: "new", // Possible compose-sms in future versions
data: {
type: "websms/sms",
number: "+38163123456",
body: "my test sms text"
}
});
Actual results:
The New SMS activity is open but the phone number is not filled in (only the SMS body). This happens in OS v1.2 preview (test on Geeksphone Peak)
Expected results:
New SMS activity is shown with filled data: phone number and sms message body.
Comment 1•11 years ago
|
||
Confirmed. I'm seeing this on v1-train as well. Got a partner compliant as well from partner engineering.
Status: UNCONFIRMED → NEW
blocking-b2g: --- → leo?
status-b2g18:
--- → affected
status-b2g18-v1.0.1:
--- → unaffected
Ever confirmed: true
Keywords: regression
Summary: SMS Web Activity call from 3dt party web apps wont transfer phone number → SMS Web Activity call from 3rd party web apps wont transfer phone number
blocking-b2g: leo? → leo+
Priority: -- → P1
Target Milestone: --- → 1.1 QE4 (15jul)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → anthony
Comment 2•11 years ago
|
||
I believe this was fixed here: https://github.com/mozilla-b2g/gaia/commit/aaafec3c79e94041db7d22d3490f8d4916faeb3a
Can you confirm with gaia@master?
Assignee | ||
Comment 3•11 years ago
|
||
That would explain why I can't reproduce today.
Marking as worksforme because of that.
Zoltan, feel free to reopen if you can still see this with a build from today.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
I don't know if this was fixed in v1.1, currently I have no way to test.
On v1.2 pre-release it is working fine with a nightly build for Peak, 16-07-2013:
nightly-images-peak-2013-07-16.Gecko-d38f55b.Gaia-759f4b2
Is it fixed also in v1.1?
Assignee | ||
Comment 5•11 years ago
|
||
From my testing, yes it is. And the commit Rick mentioned has been merged in 1.1.
Updated•11 years ago
|
status-b2g18:
affected → ---
status-b2g18-v1.0.1:
unaffected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•