Forums

RSS RSS
RE: Problem with liferay navigation menu over applet Flat View
Threads
Hi,
I have developed a portlet that includes displaying an applet (to display graphs).
If the user includes this portlet on his page, the applet then always show on top of the liferay menu, which makes it impossible for the user to navigate to other community pages (see attached file for a view of the problem).
The same thing happens if the user wants to change the layout template of the page that contains an applet.
Is there a known workaround for this problem? Is that something I need to take into consideration in the code of my applet?
Thanks for your help.
Attachment

Attachments: navigationbar.JPG (20.2k)
Flag Flag
RE: Problem with liferay navigation menu over applet
4/24/08 7:41 AM as a reply to Lionel Griache.
I've have similar situation, but the menu is being obscured by flash.
Attachment

Attachments: obscured_menu.JPG (38.5k)
Flag Flag
RE: Problem with liferay navigation menu over applet
4/24/08 10:26 AM as a reply to Eric Devlin.
front-end is not my expertise, so i'll try to find someone to address this issue you guys are seeing ...

one quick note though, can the z-index be modified for the dropdown menu so that it'll be on top of everything? this would be a change in the theme ... thoughts?
Flag Flag
RE: Problem with liferay navigation menu over applet
4/24/08 10:40 AM as a reply to Lionel Griache.
As far as Java applets go, it's a bit tough.

What you have to do is create a transparent iframe that covers the applet. Luckily there is a jQuery plugin that will do this for you. The plugin is called bgIframe, and it's available through here:
http://brandonaaron.net/jquery/plugins/bgiframe/docs/

How you would use it in Liferay is:
jQuery('.lfr-dock').bgiframe({height: 500});

And I think that will take care of it. It may need some tweaking though.


For Flash, however, the fix is quite easy. In your source where you embed flash, pass this parameter in with it:

wmode="transparent"

And that will make sure the dock sits on top of it.

Of course, let us know if that helps.

Thanks guys,
Flag Flag
RE: Problem with liferay navigation menu over applet
4/24/08 10:45 AM as a reply to Nate Cavanaugh.
Thanks. Will give it a try. Will let you know.
Flag Flag
RE: Problem with liferay navigation menu over applet
4/24/08 12:30 PM as a reply to Nate Cavanaugh.
wmode="transparent" is a winner! Thanks, that wasn't going to be my first place to dig into that problem.

Eric
Flag Flag
RE: Problem with liferay navigation menu over applet
4/24/08 12:56 PM as a reply to Eric Devlin.
Unfortunately. Not the same story with the java applet.
Did a quick test with the test page of the jQuery plugin. If I include my applet in this page, it shows again on top of everything else.
One other way to reproduce the problem in Liferay is to have a webpage display a PDF document. The PDF document will also appear on top of the navigation menu. Pb is the same with Internet Explorer, Firefox... Will continue investigating and post any update I might have.
Thanks.
Attachment

Attachments: appletpb.JPG (43.3k)
Flag Flag
RE: Problem with liferay navigation menu over applet
4/25/08 9:16 AM as a reply to Lionel Griache.
Seems like there is no way of making the applet not show on top of the menu layer.
My next option would be to customize the way the menu is displayed.
Any tip on where to start looking for this?
Flag Flag
RE: bgiframe usage
9/3/08 5:43 PM as a reply to Nate Cavanaugh.
Hi Nate,

I'm using 5.1.1

I have what is likely to be a common problem for losers like me who are on a corporate network that still uses IE6 as the standard browser.

When I view the 'Add Application' or 'Layout' dialogs and dropdown just get shown right through the guts of them and makes our theme look very 'buggy'. I have researched the solution to this problem and finally arrived here at this entry which appears to explain that if I use the jquery plugin 'bgiframe' I can resolve these problems.

My problem is that I don't have the necessary smarts to interpret your 'jQuery('.lfr-dock').bgiframe({height: 500});' to a working solution for both the Add Application ui-dialog and the Layout ui-dialog.

Would you please be able to give just a few little pointers (like where do I add this code, and what the correct code would be for fixing these two dialogs in IE6). That would be very helpful to others as well. Thanks.

PS. I searched this forum for 'bgiframe' and got no results. I searched Google for 'liferay bgiframe' and found it... weird.
Flag Flag
RE: bgiframe usage
9/15/08 6:04 PM as a reply to Luke McLean.
Hey all

I've got the same problem as Luke: stuck on IE6 and lacking the 'smarts' to fix this. Can someone please explain the correct usage of jQuery('.lfr-dock').bgiframe({height: 500}). Where should it go and how should it be modified to stop the select boxes showing through my DIVs?

Thanks,
Kenny.
Flag Flag
RE: bgiframe usage
9/16/08 10:46 AM as a reply to Kenny Ritch.
I haven't actually made the move to version 5 yet, but it seems like this might work.

1 download the plugin from http://brandonaaron.net/jquery/plugins/bgiframe/docs/
2 modify portal-ext.properties javascript.files to include the new library
3 modify javascript/javascript.js --> jQuery(document).last( jQuery('.lfr-dock').bgiframe({height: 500}); );
4 rebuild as necessary
5 redeploy as necessary
6 restart as necessary

Hope it helps
Eric
Flag Flag
RE: bgiframe usage
3/10/09 1:20 PM as a reply to Eric Devlin.
has anyone got this to work in 5.1.X? I can't seem to get it do anything different, no errors nothing....
Flag Flag
RE: bgiframe usage
3/11/09 9:06 AM as a reply to Chris Whittle.
nevermind I got it... for prosperity
https://www.liferay.com/web/guest/community/forums/-/message_boards/message/2454391
Flag Flag
RE: bgiframe usage
7/22/09 8:12 AM as a reply to Chris Whittle.
To close the problem that initiated this post, I finally decided to bann applets and replace them with Flash.
Works much better.
Flag Flag
RE: bgiframe usage
7/22/09 8:15 AM as a reply to Lionel Griache.
we actually had to dial back our use of bgiframe due to the overhead it was adding to the browser and response times...
Flag Flag