Hi Guys.. One of my users kept saying sometimes when he tries to enter a post or reply to a post the text area is like an inch tall. I never could find a problem until just now. Clicking inside that white text area closed it up completely. I was able to bring up an html window and enter and save my post. Weird and dies not do it all the time.
Screen shots attached.
Any suggestions? Thanks! 
I have seen that once or twice recently. This is all WordPress core code and I am wondering what they might have done to it in the last update.
I found that if you grab the resize handle bottom right and pull it down it tends to stay down from there on and stick.
I’ve found this in Chrome on a PC (Win 7 and 8). Resizing the window does fix it (at least until you close the browser, then it’s back to a single line).
Specifically Chrome eh? That might be where I encountered it… I will test. It will still be hard to pin down though sadly…
I know Andy said he has seen it once or twice… but I cannot seem to make it happen… Andy is on Mac and I am on pc…
and as mentioned, this is the wp editor… and I am using the 3.8 version of it since we are testing compat with wp 3.8 which should release in less than 2 weeks…
I’m on a mac, but got it running Win7 through VirtualBox and using Chrome 31.
It is not so much the depth that bothers me it is more the fact that the bottom ‘path’ bar appears half way up.
Anyway – I am trying now repeatedly using Chrome on my Mac and can’t get a repeat of the behaviour! Typical really… I will go off and try Safari as well as they are both webkit based browsers.
No – Safari is good as well. At least on a Mac.
So – can anyone confirm if they have this problem using OSX natively?
I was just going to say I’ve seen it only once, in Chrome, in OSX (10.9) and when I went to reply I got it again. It seems far more consistent in Chrome on the PC though.
Here’s a screenshot. The height is being set too low on the iframe, 28px in this case.
Thanks for the screen-shots. Nice and useful to see visual confirmation of what is being incorrectly reset by the Chrome browser and script engine.
I assume that no-one is having any similar problems with tinyMCE under Chrome when it comes to using it to write blog posts/pages…?
G’Mornig Everyone, I should add that i use Firefox the greatest majority of the time and have not seen that error in Firefox. It was the one time i used Chrome that i got the error. My forum member also uses Chrome that is having the problem.
