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.

Posts: 558
Registered: ‎11-25-2008
My Device: Not Specified
Accepted Solution

Question about capabilities of the internal browser in the Storm.

BB Storm JDE 4.7


Can someone tell me whether the internal browser is fully html 5.0 compliant?, or comment on my next statement...


I've managed to run "some" iphone web applications that use the <canvas> tag, so clearly that is supported to some degree, as is Javascript. However, some fancier iPhone webapps don't run well at all on the Storm.


Understanding what the browser is capable of is very important so we can use it to it's limit in applications where we can leverage off of what is already there, combining <canvas> with javascript AND j2me.




Guru I
Posts: 19,020
Registered: ‎07-29-2008
My Device: Passport, Playbook, 9320BES
My Carrier: Bouygues _ SFR

Re: Question about capabilities of the internal browser in the Storm.


The search box on top-right of this page is your true friend, and the public Knowledge Base too:
Posts: 558
Registered: ‎11-25-2008
My Device: Not Specified

Re: Question about capabilities of the internal browser in the Storm.

Thanks Xandrex. Your link wasn't quite right, but I did find I think what you were trying to point to is here:



Now, one thing to be aware of (for those following this) is that your wireless access goes through a server and it knows what kind of information that is going across the http protocol. It translates a lot of this into before sending it into the airwaves to make it more efficient (a good thing). Here are some translations that occur in real time....


Javascript -> javascript bytecodes.

Many graphic file formats are converted into .png file formats. tiff is supported (not in normal browsers without a plug-in)

JAR files are converted into .cod.

Large images are scaled to fit the screen or a proportion thereof.

html and xhtml are converted to a format similar to WBXML


SVG -> PME (a proprietary binary format that the blackberry handles well).

WTAI call links supported.

Screens and windows are supported in Javascript.

There are meta tags that can be useful too.


Much of this stuff is for MDS development.

No info on the <canvas> class and why it seems to be working.


Some other great links are here:



I need to do more research on canvas tags....still unsure if it's accepted. I did discover shapes tags tied to




Posts: 558
Registered: ‎11-25-2008
My Device: Not Specified

Re: Question about capabilities of the internal browser in the Storm.

I finally found the answer....we really don't support the <canvas> tag, though if we supported this, the power we would have in our browser would be so much more. I really can't believe that we don't support it.


Check out this site and click on any example. This shows what could be possible with a tiny little bit of browser capability added to our browser....one tag only in fact....




This closes this. I have to recommend this to the blackberry "bosses" as a feature that we need to compete.