java plugin shows white field instead of what it is supposed to when connected from a simple xul application, that is just running the page fullscreen

RESOLVED DUPLICATE of bug 534355

Status

()

RESOLVED DUPLICATE of bug 534355
9 years ago
9 years ago

People

(Reporter: postnalista, Unassigned)

Tracking

1.9.2 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100216 Fedora/3.5.8-1.fc12 Firefox/3.5.8
Build Identifier: firefox 3.6 xulrunner-1.9.1.2

ww have a simple xul application (it is only showing the page fulscreen), that connects to a web ticket shop. The web shop uses a java applet to show seat info. after upgrade to firefox 3.6 and xulrunner-1.9.1.2 the space where the picture with the seats should be is just blank. the page works ok from firefox window. 

when you turn on java console it looks like everything is ok, also if you compare it to the output from the console run from the browser, they are almost identical.

and yes i know that there is a new java plug-in for firefox 3.6

Reproducible: Always

Steps to Reproduce:
1.connect to example page with browser
2.connect to example page from xul app
3.compare result
(Reporter)

Updated

9 years ago
Component: General → XUL
Version: unspecified → 1.9.2 Branch
How exactly are you doing the "connects to a web ticket shop" thing?  Where are you loading the http URI?
(Reporter)

Comment 2

9 years ago
We are loading HTML page which contains an java applet

its a very basic xul application that has only one purpose. Show the page fullscreen. We are using this on touch monitors with just 1024x768 resolution, so we have to use as much screen as possible.

As i said the applet shows fine in Firefox but fails to show anything if run through the xul application.
> We are loading HTML page which contains an java applet

Yes, but how exactly?  A <xul:browser>?  A <xul:iframe>?  The toplevel chrome window?  Something else?
(Reporter)

Comment 4

9 years ago
where would i find such info. I didn't write the application and i don't really know how it works.

here is the content of chrome/content/main.xul, which is basicly the only file that has any relevant data in it.

<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>

<window 
    id="main" 
    title="My App" 
    width="1024" height="768"
    hidechrome="true"
    sizemode="maximized"
    fullScreen="true"
    onload="window.setTimeout( function(aWindow) {
    aWindow.fullScreen = true;
    },0,window);"


    
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">

  <!--<button label="Zapri" oncommand="window.close();"/>-->
  <iframe id="myFrame" flex="1" src="http://petrol.eventim.si/" />

</window>
>  <iframe id="myFrame" flex="1" src="http://petrol.eventim.si/" />

That's the information I needed, thanks!  That needs to have a type="content" on it; that should incidentally fix the rendering issue.  As written now it's actually a security bug...
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 534355
(Reporter)

Comment 6

9 years ago
where would i find such info. I didn't write the application and i don't really know how it works.

here is the content of chrome/content/main.xul, which is basicly the only file that has any relevant data in it.

<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>

<window 
    id="main" 
    title="My App" 
    width="1024" height="768"
    hidechrome="true"
    sizemode="maximized"
    fullScreen="true"
    onload="window.setTimeout( function(aWindow) {
    aWindow.fullScreen = true;
    },0,window);"


    
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">

  <!--<button label="Zapri" oncommand="window.close();"/>-->
  <iframe id="myFrame" flex="1" src="http://petrol.eventim.si/" />

</window>
(Reporter)

Comment 7

9 years ago
forget the last comment, i accidentally hit refresh
(Reporter)

Comment 8

9 years ago
the solution you suggested works great. 

Thanx for the help.
You need to log in before you can comment on or make changes to this bug.