This is created as a follow-up bug of Bug 934449. I have created a really simple test case here, https://github.com/RudyLu/gaia/commit/57354b0253c9c65713ce4ed9dff1a1c40dd34b7d , which will focus an input and then call the "pick contact" activity. On v1.1, the keyboard would disappear after a while the new activity is loaded, but not on current Gaia master.

Hi Alive, Do you happen to know if we have changed anything about focus after launching an activity? Thanks.

Also ni Gary to see if he's interested in taking a look.

I think we should blur / focus when inlineActivity is launched/killed but I don't why we don't in current master.

Hi Rudy, I'll take a look.

Well, should throw a blur event from platform. Gary, can you verify whether that happens?

Any update? Thanks!

Hi Alive, please help to review this patch. Adding 'activitywillopen' and 'activitywillclose' event handler. Thanks.

Comment on attachment 8349890 [details] pull request: https://github.com/mozilla-b2g/gaia/pull/14831 r+ if use new event name

Thanks Alive, I've addressed your comment https://github.com/mozilla-b2g/gaia/pull/14831/files Travis passed: https://travis-ci.org/mozilla-b2g/gaia/builds/15692845 land in master: https://github.com/mpizza/gaia/commit/3364f21ad0987bb327d39ed2a9e46aeceed65b84

Gaia master hash is: e8dfed06a8524c0d72c0c96c83341562754164fc

Gary, alive, would it be easy to uplift this in 1.3? Should we request an approval?

Yes, activity* event comes from ActivityWindow which is also in 1.3

Hi Ivan, I've set this issue to v1.3?. Should we uplift this issue to v1.3 after being nominated v1.3+ ?

Thanks! I just duped another consequence of this bug here then :)

(In reply to GaryChen [:GaryChen][:PYChen] from comment #13) > Hi Ivan, > I've set this issue to v1.3?. > Should we uplift this issue to v1.3 after being nominated v1.3+ ? I promoted this to v1.3+ based on comment 12 because this one looks to me the regression and the fix should be in v1.3 as well.

I was not able to uplift this bug to v1.3. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1.3, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with: git checkout v1.3 git cherry-pick -x -m1 e8dfed06a8524c0d72c0c96c83341562754164fc <RESOLVE MERGE CONFLICTS> git commit

travis passed: https://travis-ci.org/mozilla-b2g/gaia/jobs/16908216# landed in v1.3: https://github.com/mpizza/gaia/commit/984223b294384d7c512755f395dc5f0bb9665455

revert it first, I make some mistake here. https://github.com/mozilla-b2g/gaia/commit/a81ccdc53e45a6adeaae423e104e91bcc1e12b0e

Thanks for digging out this problem and passed the information. We (Taipei QA) are participating in QA workweek (1/12~1/17). So we still don't have time to verify it. We will verify it in a few days. Thanks.

Hi Alive, Please help to review this v1.3 patch. Thanks.

travis passed: https://travis-ci.org/mozilla-b2g/gaia/builds/17259371 patch landed in v1.3: https://github.com/mpizza/gaia/commit/21a23f8386bf997bcda3b9c8da23593f044c2055

Thanks for the help! I cannot reproduce the bug that comment 20 mentioned. Verified it. * Verified Build: (Device -> Buri) - Gaia 47049555282a9a01fb60d1e1421b57e2810c96f5 - Gecko http://hg.mozilla.org/releases/mozilla-aurora/rev/6f7dfe36ab6c - BuildID 20140121004137 - Version 28.0a2 * Result: - Cannot reproduce it.