The purpose of this patch is to retain the focus when the system dialog is focused again by reordering the hierarchy. What we could do more is: record document.activeElement when FxAccounts is deactivated, and when it's being activated again, only call focus if the last document.activeElement is an input. Note: the patch is containing some change from bug 1079748; I will clean it up after bug 1079748 is landed. Lemme know what you think, and if there is a better to communicate with FxAClient I am listening. One more: Not sure how to integration test this; we don't have a keyboard library to simulate 'typing' behavior now. :/

Comment on attachment 8518066 [details] WIP I am afraid that I don't have enough knowledged about what the hierarchyManager does and how that affects to the FxA dialog, so I'll defer the feedback about the global picture to Etienne. WRT the FxA code, looks good to me. And AFAIK postMessage is the only way we have to communicate with the dialog content once it is loaded.

Comment on attachment 8518066 [details] WIP Definite feedback+! Can we get this covered by a marionette test with a 'mozFxAccountsUnsolChromeEvent' dispatch?

Firefox OS is not being worked on