yup, it is blocked by the full CC commits (3 times!!?) resulting from resizing the Client window when IME is shown.

logs from --vmodule="blimp_message_pump*=2, blimp_engine_session*=2, blimp_connection*=2"


===> Client IME shows, resize to Engine. 
[1291:1310:0325/143735:VERBOSE2:blimp_message_pump.cc(59)] OnReadPacketComplete, result=<BlimpMessage type=TAB_CONTROL subtype=SIZE size=768x466:2.00 byte_size=23>
[1291:1291:0325/143735:VERBOSE1:blimp_engine_session.cc(294)] Resize to 768x466, 2

===> full commit once
[1291:1310:0325/143746:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=1327690>
[1291:1310:0325/143746:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=17>

===> full commit twice??
[1291:1310:0325/143757:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=1325432>
[1291:1310:0325/143757:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=17>

===> full commit 3rd time?
[1291:1310:0325/143808:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=1325432>
[1291:1310:0325/143809:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=17>
[1291:1310:0325/143809:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=7 target_tab_id=0 byte_size=17>
 

The commits are expected since the engine requests them, as discussed in crbug/598082. We should not resize when the IME is shown to avoid a re-layout.

[Bulk edit]

This Blimp bug is targeted to M-52, which ends today.  Please change the target milestone to M-53 (which ends June 30) if appropriate and if your team lead signs off.  Any items still targeted to M-52 on Monday will have their milestone tags removed.

Please do *not* remove the label Blimp-M52-Proj-Scope if it exists on this bug; that is a scope tracking label only.  Similarly, do not add Blimp-M53-Proj-Scope yet either; I'll take care of that.

Ping me with any questions, thanks!

shaktisahu@ will ping bruno about this to ensure that we have a clear path forward from a UX perspective.

Shakti, are you intending to resolve this, or should we WontFix pending the client-integration work completing?

Shakti will ping Bruno first, and then we'll see what he says about at least finding a way for how we want this to behave. Based on that we should know more on how this would be affected in the integration with Chrome.

For now resizes the content area when entering text in a webpage.  Will push the more comprehensive fix of not doing a full round trip resize until later.

[Bulk edit]

Setting tracking label Blimp-M54-Proj-Scope.  This label is for scope tracking purposes only and should not be added / removed from any bugs, even if we add additional bugs to M-54 scope, or remove this bug from M-54 scope.

Closing this out.  We're going to move the IME to a popup for now to start to get a feel for how that works and also to bypass the resize issues until we actually want/need to fix them.

Actually even with the popup we don't want to resize the content.  But I don't think we care about keeping the text box on the page with that UI.  Moving to M-55 though.

Fixed with popup. There is no more need to resize the content.
CL : https://codereview.chromium.org/2292343002/