Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development

Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.

New Developer
Posts: 2
Registered: ‎10-01-2008
My Device: Not Specified

In OS 4.5, HTML textarea does not work if it contains content

Hopefully I'm missing something obvious - but, users of our mobile webmail site have reported that they can not reply to messages.  They all have user agents like "BlackBerry8320/4.5.0.x...".


I've trimmed down the page to the following HTML.   If the textarea is over 12 or so rows, and it contains content, no content after the textarea is displayed in the browser.


Does anyone have any information on this - maybe a workaround?


Thanks much


<title>BlackBerry Compatibility Test Page</title>

                <textarea name="test" rows="13">Test textbox
With content</textarea>


                <input type="submit" name="action" value="Send"/>


BlackBerry Development Advisor
Posts: 15,887
Registered: ‎07-09-2008
My Device: BlackBerry PRIV
My Carrier: Bell

Re: In OS 4.5, HTML textarea does not work if it contains content

I have been able to reproduce this on BlackBerry handheld software version 4.5.0.  It worked fine in version 4.3.0 and 4.6.0, so it appears that the problem has been addressed.


You could detect the BlackBerry Browser version and limit the textarea to 12 lines if the version is 4.5.0.  The following link explains how to detect this.


How To - Retrieve information about the BlackBerry Browser
Article Number: DB-00435


Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
New Developer
Posts: 2
Registered: ‎10-01-2008
My Device: Not Specified

Re: In OS 4.5, HTML textarea does not work if it contains content

Thank you for your response.

The problem seems to be more complicated than just a 12 line maximum on textareas.  For example, we were only able to make it work in our mobile webmail site when it is 5 lines - which isn't really enough to compose an email in.

We've seen a few user complaints about this and I'm worried it's going to get much worse as 4.5 becomes more popular.  If there's anybody who knows exactly what the cause & workaround is that would be super helpful.  In the mean time, I'll keep digging as time allows and report back if I find anything.
New Developer
Posts: 1
Registered: ‎07-01-2009
My Device: Not Specified

Re: In OS 4.5, HTML textarea does not work if it contains content

Are there any updates on this issue? I'm experiencing exactly the same problem on the browser.


I can make my page work if I restrict the text in the TEXTAREA to approximately 20 characters, but this is obviously not an optimal solution.


I'm also testing in the 8310 ( simulator - this actually causes a JVM exception in the simulator when I try and load the page.