993935 - [keyboard refactor] layout manager should abort the loading of previous layout when there is a second one

Status: RESOLVED INVALID

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

Description

[Tim Guan-tin Chien [:timdream] (please needinfo)]

+++ This bug was initially created as a clone of Bug #956175 +++

I didn't review this patch correctly. The behavior described by this unit test is incorrect.

https://github.com/mozilla-b2g/gaia/commit/4645b8da5a9cf25795313b20a56bad67225786c5#diff-b4732e6601b789fba0e97cd98df1b096R68

The handleLayoutLoaded() should not be called twice when the layout to handle is not the last one being called.

We can also make KeyboardApp check it's currentLayoutName instead. Rudy, what do you think?

Comment 1

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

Yes, I also consider the API behavior as you said when writing this part of code, but at the end, I chose to make the API respond with handleLayoutLoaded() each time when the client code request a layout.
I think the client should control the calling of layoutManager.call() and handle handleLayoutLoaded() accordingly.

Please let me know if you have any other suggestions.