[Pidgin] #4986: automatic chat input field resizing should be optional, regression from 2.3

[Pidgin]

#4986: automatic chat input field resizing should be optional, regression from 2.3
---------------------------+------------------------------------------------
  Reporter:  swbrown       |       Owner:                   
      Type:  enhancement   |      Status:  new              
  Priority:  minor         |   Milestone:                   
 Component:  pidgin (gtk)  |     Version:  2.4.0            
Resolution:                |    Keywords:  chat input resize
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by G-sus):

 Hello,

 the current resizing behaviour of the text input box also causes troubles
 in combination the third party plugin
 [http://www.civil.iitb.ac.in/~d3sachin/compwork/lazybums/lazybums.php
 LazyBums]. I'm referring to Pidgin on Windows XP SP2 as I couldn't test
 this on others OSes.

 LazyBums provides configurable buttons that send often said words or
 phrases to the chat partner by clicking the according button. This button
 bar is put at the bottom of the conversation window, actually (as of the
 previous versions of pidgin) right below the text input box, using about
 the space of 2 lines of text. Since this box is not resizable anymore by
 simply dragging the divider with the mouse, the conversation window often
 appears without the text input box - see the
 [http://developer.pidgin.im/attachment/ticket/4986
 /Screenshot_conversation-window_2.4.0.TIF screenshot I attached]. This
 happens rather sporadically, I'm not sure, but it seems to occur always
 when a message was sent to the systray in away mode and then later opened
 by clicking the blinking "message arrived" icon in the systray. It appears
 to be independent from the protocol used.

 As a workaround I have to check and uncheck the option "Show Formatting
 Toolbars" in the options menu of conversation window, afterwards I have
 the text box back and usable.

 Not sure if this is solely a pidgin issue or rather an issue of the third
 party plugin. Just wanted to state it for the sake of completeness.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/4986#comment:126>
Pidgin <http://pidgin.im>
Pidgin