Visualization bug (statement input area in combination with a child block and an comment entry of the child)

What steps will reproduce the problem?
1. Open the code example workspace
2. Select a procedure or if block
3. Add a block at the statement input area
4. Right click on the child block and "Add Comment", write some text and hide 
the bubble if you like.
5. right click on the parent block and choose "collapse block"
6. "expand block" once again.

What is the expected output? What do you see instead?
I expect the block to expand to its former shape, but unfortunately just the 
procedure name or "if" is visible nothing else changes. Only a reload of the 
page (F5 or switching to the xml tab and back) resolve the problem and the 
block is expanded once again.

What browser are you using?
Ubuntu 12.04
Google Chrome Version 26.0.1410.43

Please provide any additional information below.
Another observation:
Whenever a block has lots of content (many blocks attached to an input area) 
users, who want to write a comment, have to scroll down to see the bubble and 
type in text. In order to hide the bubble again they have to scroll up once 
again. Since mouse wheel scrolling is not implemented the scrollbar scrolling 
is cumbersome and even dragging the workspace is especially, if there are 50, 
100 or more blocks attached to a statement input area (e.g. the case for a 
procedure, etc.) not as intuitive as native scrolling. I have to mention that 
this is my opinion and I do not know how other people think about that, 
especially beginners.

Suggestion: Show the bubble above the selected block. Since you have to scroll 
up to the top of the block to click on the comment icon anyway, it makes sense 
to show the bubble there.
Additionally add scroll functionality (I believe this would increase the 
usability a lot, but I have no proofs for that). 

best regards
Marc Wollenweber

Original issue reported on code.google.com by borntob...@googlemail.com on 29 Mar 2013 at 2:30

JakAttack909 / blockly

Visualization bug (statement input area in combination with a child block and an comment entry of the child) #133