Closed Bug 917191 Opened 11 years ago Closed 11 years ago

[SMS]keyboard is not display when SMS app is open from contact app

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 914100

People

(Reporter: mu-ota, Assigned: alive)

References

Details

(Whiteboard: burirun3)

User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36

Steps to reproduce:

1.contact app launch
2.select contact and tap sms button
3.sms app is open and focus on compose


Actual results:

focus on compose but no keyboard


Expected results:

focus on compose and keyboard is displayed
tap compose but nothing happens.
Once tap another area, focus changes and re-tap compose, keyboard is displayed.

On 9/F ver, this issue is not happen.
Reproduced.

Hi new comer,
What does the '9/F ver' you mean?
Hi Alive

My previous environment isn't reproduced.
My previous environment is following

branch: master
gaia: e217f6e01d424be2d5b31bd5fcf53bc7915a40a2
Sorry I've mistake my report.

This issue is reproduced before above version.
I have mistake in statement.
This issue is reproduced when SMS app doesn't work on.
When SMS app is working on background, this issue is reproduced.
(In reply to kenzo Ohta from comment #4)
> Sorry I've mistake my report.
> 
> This issue is reproduced before above version.
> I have mistake in statement.
> This issue is reproduced when SMS app doesn't work on.
> When SMS app is working on background, this issue is reproduced.
When SMS app is working on background, this issue is "not" reproduced.
Taken first.
Assignee: nobody → alive
I think I've seen the keyboard showing sometimes, but then I didn't have the suggestions.
Blocks: 1.3-keyboard
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: burirun3
This works for me on a recent build. I think this was fixed by bug 914100, so duplicating there.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.