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 Contributor
Posts: 4
Registered: ‎07-04-2011
My Device: PlayBook
My Carrier: Fido

Bug w/Flash causing Keyboard display.

When my Flash application is accessed through the Playbook's browser, the native keyboard begins to display and then dissappears when a text link is triggered by the Flash Player even if I prevent the default behaviour for the TextEvent, and stop its propagation. For example:


var t:TextField = new TextField();

t.htmlText = '<a href="http://google.com/">Google</a>';



function eTextEvent(e:TextEvent):void






From a usability perspective this is incredibly irritating, as the keyboard should only display when the user clicks within a field that allows for text input. Does anyone know how to prevent the Playbook's keyboard from displaying in this case?