Welcome!

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

Reply
New Developer
Posts: 3
Registered: ‎05-10-2009
My Device: Not Specified

critical problems in PlayBook web browser with fullscreen iframes, window.open/opener, and PDF

We've been looking forward to the PlayBook / RIM Tablet OS with its Flash support but there are some critical issues for us that we hope will soon be resolved since they work more as expected on an Android browser (e.g. Samsung Tablet):

 

1. IFRAME tags behave strangely in fullscreen mode, where it seems to fullscreen either the IFRAME or the PARENT window but doesn't seem to be able to display both PARENT and IFRAME together as it's supposed to in fullscreen mode.  It seems to work as expected in non-fullscreen mode.

 

2. There are problems with var childWin = window.open("about:blank", ...) followed by trying to set childWin.location.href = "http://the-actual-site.net/; which works across desktop browsers and the Android tablet browser but not the PlayBook tablet browser.  ( http://www.w3.org/TR/Window/ : When the href attribute is set, the Location's window MUST navigate to the newly set value.)  Also, the window.opener does not seem to be set or available properly to the parent window.

 

3. PDF should open more naturally either to an external or internal viewer rather than Save As... and then forcing the user to go find and open it themselves.

 

It's great to have Flash integrated, but PDF is also a mainstay of the web as are iframes and window.open.

 

It makes it easier to recommend the PlayBook when these pieces work.

 

Highlighted
New Developer
Posts: 3
Registered: ‎05-10-2009
My Device: Not Specified

Re: critical problems in PlayBook web browser with fullscreen iframes, window.open/opener, and PDF

Further investigation shows this is a conflict between mixed Flash/HTML/etc. content and the double-tap "feature" that expands a Flash component from within the browser to fullscreen.  It seems to lose mixed HTML content that may have been overlayed on the Flash component, or lose other related Flash components on a multi-component page.

 

Searching for a way to disable this "feature", ...