|
I'm working on an application where we have used panelLayout elements to define key parts of the screen (ie masthead, content, footer) and within the content area nested panelSet elements so that parts of the screen can be resized.
I've tried to load the app in FF3 this morning and found that the content area (the panelSet) does not display. Checking the code i've found the following issues affecting display:
- The element style for the panelSet element is set to visibility:hidden by the backbase engine
- additionally, the panels do not get a height or width despite it being declared in the parent element attributes.
In summary, the panelSet widget does not display because it is not rendering correctly. To further test this i attempted to launch the backbase demo in FF3 and found that none of the demos will load.
Any insight on how to fix this? (and no, upgrading to 4.2 at this time is not an option).
PanelSet and Firefox 3 in Backbase 4.1
11 July, 2008 - 16:18 — EmielHi bblyth,
I have tried the demos(4.1) but I am able to see them in FF3. Can you be a little more precise in what is not working or give me the structure of your panelSet?
?!!
11 July, 2008 - 17:12 — bblythFF3 Beta, or the full release???? I've tried everything i know on the demo and can't get anything but a white screen...
I'm running FF 3.0 on Windows XP. When i go to the 'demo' folder and select the 'explorer' and click on 'index.html' i get a white screen in the browser. I can view source and see that indeed the content loaded, but i can't actually see the content.
Confirmed
14 July, 2008 - 09:14 — nick@backbaseI've tested with Firefox 3.1 and see the same issue. It looks like a security restriction in Firefox when accessing the file system. If you set up a file server and access the demos via this they will work correctly (e.g. localhost/.../Backbase_4_2_1/demos/explorer).
PanelSet and FF3 - a deeper look
24 July, 2008 - 11:21 — bblythFirstly, Nick, thanks for the info. After setting up the 4.1 demo as a project in eclipse i was able to look at it via FF3, and the widgets did indeed render correctly - with a small caveat (see below). Of course, this has only fueled the fire of my curiosity as to why the panelSet in my app won't render in FF3. I've been digging around and playing with code and here are my observations - perhaps you can connect the dots for me... I may not be able to see the forest for the trees with this one.
1 - the demo
When viewing the panelSet or even the panelLayout from the demo the widget does not initially display. Looking via firebug i can see it has loaded, but the visibility is set to hidden, sizes are not declared, and most strange, the splitter is not rendered at all - ie the code doesn't exist - the div's are never created. If i select the tab in the demo to see the source or edit and then click back to see the example, it DOES render, including the splitter.
2 - My app.
In looking via firebug i can also see that the panelSet does render. But just as in the demo, visibility on the parent is set to hidden, sizes are not declared for the panels and the splitter elements are no where to be found. It's as if the script that renders the panelSet and panelLayout elements is getting hung halfway through execution.
I've tried removing the splitter, i've tried non-wild card fixed heights and widths. I've removed all child content. I've removed all parent content. It seems that no matter what i do i get the exact same result in FF3 for both the demo and my app for the panelSet and panelLayout widgets - the backbase renderer simply stops before it completes the panelSet.
Any ideas on what could be going on???