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 Member
Posts: 1
Registered: ‎01-30-2012
My Device: BB7
My Carrier: None

BB7 Simulator, (9900) webkit 3d issue

I have encountered an issue testing the Sybase SUP (Sybase Unwired Platform) client application when using our custom date/time/datetime picker control. It seems that the control is created but cannot be made visible. This control uses webkit 3D transforms like this:


ul.style.webkitTransitionTimingFunction = 'cubic-bezier(0, 0, 0.2, 1)'


this.slotEl[slot].style.webkitTransform = 'translate3d(0, ' + pos + 'px, 0)';


When I test the same control with all the webkit 3d stuff commented out, the control can then be seen ... but of course it doesn't behave properly.


Is this a known issue or is there some fix or workaround that I could use?