SWFObject is a commonly used JS library for instantiating Flash objects universally.  Flash objects are considered to be “windows” on top of the browser and this is why they cover the submenus by default. This can be easily changed however. SWFObject offers two distinct methods to embed Flash Player content:

  1. The static publishing method embeds both Flash content and alternative content using standards compliant markup, and uses JavaScript to resolve the issues that markup alone cannot solve.
  2. The dynamic publishing method is based on marked up alternative content and uses JavaScript to replace this content with Flash content if the minimal Flash Player version is installed and enough JavaScript support is available (similar like previous versions of SWFObject and UFO).

If you use the static publishing  method you just have to add the transparent parameter in SWFObject.  For example if the code of  SWFObject looks like the following:

<script type="text/javascript">

var so = new SWFObject("movie.swf", "mymovie", "200", "100%", "7", "#336699");


you have to add the following line of code:

so.addParam("wmode", "transparent");

so that your code look like the following:

<script type="text/javascript">

var so = new SWFObject("movie.swf", "mymovie", "200", "100%", "7", "#336699");

so.addParam("wmode", "transparent");


If you use the dynamic publishing method you need to apply the transparent parameter too. In this method you use the embedSWF function so as to embed your SWF with JavaScript. The definition of embedSWF is the following: swfobject.embedSWF(swfUrl, id, width, height, version, expressInstallSwfurl, flashvars, params, attributes, callbackFn) where:

  1. swfUrl (String, required) specifies the URL of your SWF.
  2. id (String, required) specifies the id of the HTML element (containing your alternative content) you would like to have replaced by your Flash content.
  3. width (String, required) specifies the width of your SWF.
  4. height (String, required) specifies the height of your SWF.
  5. version (String, required) specifies the Flash player version your SWF is published for (format is: "major.minor.release" or "major").
  6. expressInstallSwfurl (String, optional) specifies the URL of your express install SWF and activatesAdobe express install. Please note that express install will only fire once (the first time that it is invoked), that it is only supported by Flash Player 6.0.65 or higher on Win or Mac platforms, and that it requires a minimal SWF size of 310x137px.
  7. flashvars (Object, optional) specifies your flashvars with name:value pairs.
  8. params (Object, optional) specifies your nested object element params with name:value pairs.
  9. attributes (Object, optional) specifies your <object>'s attributes with name:value pairs.
  10. callbackFn (JavaScript function, optional) can be used to define a callback function that is called on both success or failure of embedding a SWF file

So if the code of your SWFObject looks like the following:

<script type="text/javascript">

swfobject.embedSWF("myswfobject.swf", "mycontent", "935", "300", "9.0.0");


you have to replace it with the following one:

<script type="text/javascript">

var expressInstallSwfurl = {};

var flashvars = {};

var params = {wmode:"transparent"};

var attributes = {};

swfobject.embedSWF("myswfobject.swf", "mycontent", "935", "300", "9.0.0", expressInstallSwfurl, flashvars, params, attributes);


By adding the transparent parameter as described above, the submenus will always appear above SWFObject objects on all browsers.

Tags: , , , , , , , , , , , , , , , , , , ,


Hey everybody!

We are happy to inform you that we have released the latest version of AllWebMenus Pro, version 5.1 Build #784!

What's New:

- Fixed an issue in which, when a submenu appeared and an Unfold effect was used, then some scrollbars appeared in IE8 in Vista only.

- Fixed an issue where the opacity didn't work at all in Firefox 3.5.

- Fixed an issue where the Sticky Submenus option didn't work properly with sliding submenus.

To download the latest version, please visit:


Tags: , , , , , , , , ,


The most important factor that determines the size of the menu is the content of the items. If you want to reduce the size of your menu you should keep in mind that the menu must have at least the necessary size for the content of the items to fit inside. If the content is large, then you should first of all reduce the size of the content.

The properties that determine the size of each item and the menu are the <Minimum Width>in the Main/Sub/Sub+ Group Style Editor (if you want to increase the size, perhaps this is the only property you should change), the <Size> in the Main/Sub/Sub+Items Style Editor and also the <Text Margin> and the <Content Padding> in the Main/Sub/Sub+ Items Style Editor.

1. How to specify the Minimum Width property of a group.

1. How to specify the <Minimum Width> property of a group.

2. How to speicfy the Size property of the items of your menu.

2. How to speicfy the <Size> property of the items of your menu.

3. How to specify the Text Margin property of the items of your menu.

3. How to specify the <Text Margin> property of the items of your menu.

4. How to specify the Content Padding property of your menu items.

4. How to specify the <Content Padding> property of the items of your menu.

Also you can check/uncheck the "Uniform Items" option in the <Type> property of the Main/Sub/Sub+ Group Style Editor that forces all items to have the same size - the size of  the largest item. You can modify the values of these properties and change the size of the items.

5. How to specify the Uniform Items option of a group.

5. How to specify the "Uniform Items" option of a group.


Finally, If you just want to widen the menu, you have only to change the <Minimum Width> property of the Main Group Style in the Style Editor.

Tags: , , , , , , , , , , , , , , , , , , , , , , ,


When you build a menu in AllWebMenus Pro application, you apply a theme to this (usually the default one).

1. How to apply a built-in Theme in your menu.

1. How to apply a built-in Theme in your menu.

The Themes that do not contain images and are text and color based can of course be customized by the application; you just need to edit the <Background Color> property (and perhaps any other property that involves colors) in all the Available Styles of the Style Editor (i.e. Main Group Style, Main Items Style, etc...).

2. How to change the Background Color property.

2. How to change the Background Color property.

The Themes that do contain images cannot be customized color-wise within the AllWebMenus Pro. You can however customize the images that the menu is using (you can find these images in the NameOfThemes-assets folder which resides in the Theme Gallery\Vertical or Theme Gallery\Horizontal folder under the installation folder of your AllWebMenus Pro application (i.e. C:\Program Files\AllWebMenus5\Theme Gallery). Open the images with your favorite image editor and change their color, save them (it is recommended to keep backup files of the default Theme Packs of AllWebMenus Pro) and use them in  your menus!

Of course you can also create your own images from scratch, according to the needs of your website  and use them in the application to create your own menus - even your own Themes. You can find all the appropriate information about how to use your own images in your menu through your AllWebMenus Pro application to Help -> What is... -> The Image Manager.

In addition to the built-in Themes of the program, you can also purchase from the various Theme Packs that we have created. You can have a look at the Theme Packs here: http://www.likno.com/awmthemes.php. You might also be interested in the Templates we have also created and contrary to themes, menu templates are complete .awm projects with special images, features and content that cannot be themed but provide added functionality: http://www.likno.com/awmtemplates.php.

Tags: , , , , , , , , , , , , , , , , , , , , ,


This event is called the "Hanging Menu" effect. The "Hanging Menu" effect is an IE-only bug that can be solved by placing the Linking Code instance of the menu right before the </body> TAG.

In more detail, IE is loading pages in a different way that other browsers. It first loads the structure and then it loads all the text and images. The result of this is that you get the "awmAnchor" with the structure (hence the menu shows), but the whole table is still empty and concentrated in the top-left conrner (and your Anchor is there too!).

You may have noticed cases where you have pictures in your webpages and the image-holder box changes size when it loads the image (it's the same thing).

Tags: , , , , , , , , , , , , , , , ,


© 2009-2013 Likno Blog – Drop-Down Menus, Javascript Menus, CSS Menus, jQuery Scrollers/Sliders, Modal Windows