Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Understanding unordered list behavoir and House MenuUnderstanding unordered list behavoir and House Menu
Previous
 
Next
New Post
1/31/2008 1:39 PM
 

I'm sure this is some standard idea I'm missing relating to CSS and Unordered lists.  I'm attempting to understand using unordered lists for menus(using housemenu from houseofnuke.com).  To help learn it I've created a simple page, couple wrappers and the house menu.  I"m attempting to display it horizontally, and slowly adding bits of code to the CSS to see what changes.  This is my way of learning, I'm sure it's similar for most of you. 

The behavior of unordered lists in IE7.0(not sure if earlier versions also), in standards compliance mode baffles me.  To view the behavior I've created a page with drop down sub menus(hover over the "skin" menu) here:  http://www.dnnreactor.com/Skins/tabid/186/Default.aspx .  Actually no need to hover, I didn't put that part back in yet.  it's pretty much stripped down.

The Why I'm looking for today, is...WHY the heck is there a big white box that says FALSE in my Unordered list, when it contains a list item containing an unordered list.

I'm using HouseOfNuke's house menu, but this can be duplicated with just straight HTML, and does not exhibit this behavior in Firefox(of course).  I threw a couple borders around certain parts to highlight the area.  notice the "false" area isn't highlighted, it's just like IE decided to throw it in there, it's not in the source view even.

 

Here is the ASCX file:

<%@ Control Language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Skins.Skin" %>
<%@ Register src="/Portals/0/~/DesktopModules/HouseMenuSkinObject/HouseMenuSkinObject.ascx" tagname="HouseMenuSkinObject" tagprefix="uc1" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<div id="ControlPanel" runat="server">
</div>
<div id="wrapPage">
<div id="wrapHeader">
</div>
<div id="wrapMenu">
<uc1:HouseMenuSkinObject ID="HouseMenuSkinObject1"
Scope="-1"
ShowAdmin="true"
IsRecursive="true"
Orientation="h"
CssElementId="HouseMenuNav"
runat="server" />
</div>
<div id="wrapBody">
<div id="wrapContent">
<div id="ContentPane" runat="server">
</div>
</div>
</div>
</div>

And the CSS:

body
{
font-family: Arial, Helvetica, sans-serif;
font-size: 1em;
}
#wrapPage
{
width:90%;
margin: 0 auto;
}

#wrapMenu
{
width:100%;
background-color:Gray;

}
#HouseMenuNav
{
border:0px;
padding:0px;
list-style:none;
float:left;
white-space:nowrap;
}
#HouseMenuNav ul
{
width:100%;

}

#HouseMenuNav li
{
border:solid 1px black;
float:left;

}
#HouseMenuNav li ul li
{
border:solid 1px red;
float:left;

}


Josh Martin

 
New Post
1/31/2008 2:32 PM
 

Yeah, that one's a real nutter... Viewing in FF w/ Webdeveloper toolbar (helps me pick apart styles and cascade issues) maybe it's an issue with the LI#HouseMenuNavCurrentItem style... still trying to figure out a "why" though... however I did notice this in the CSS:

border-top-width: 1px;
border-right-width: 1px;
border-bottom-width: 1px;
border-left-width: 1px;
border-top-style: solid;
border-right-style: solid;
border-bottom-style: solid;
border-left-style: solid;
border-top-color: black;
border-right-color: black;
border-bottom-color: black;
border-left-color: black;

To save yourself some extra typing, you can also use:  border: 1px solid black;  I haven't run into any x-browser issues using this shorthand, but if someone has a correction, please let me know.

SB


Wells Doty Jr
Online Content Development
 
New Post
1/31/2008 6:41 PM
 

I use the web developer toolbar also, but in firefox the problem doesnt' exist.  it msut be with IE.  Also I think your using the IE toolbar to get my border setttings 'cause they are all just one line in the code itself..I think IE dev toolbar blows it all up like that.  not sure...but thanks for the tip.

If I use some pre-written CSS for teh menu from say dnncreative, they are getting rid of it somehow, but I wanna know how :->.  The idea of pre-written css from someone else sounds great, but it really doesn't help me to understand much unfortunatly, and I don't want to be bound to copyign bits of code I don't understand all the time :-<

Well...thanks for your time looking into it for me, it's much appreciated.  If I figure it out I'll post it :->

 


Josh Martin

 
New Post
1/31/2008 6:45 PM
 

well..I just looked at it with the IE toolbar and notice that there is an iframe jammed in there...must be a house thing?

Anyhow, here is what I've come up with:


The "how to" prevent the issue. Looking through house menu's sample CSS styles, now knowing that there some wierd Iframe popping in there somehow..I noticed this line in the sample CSS, and pasted it into my dev css and it removes the iframe from view. I still wish I knew what caused it, and why, I'm assumign it's some javascript stuff.

Anyhow here is the piece of code in the "houseofnuke" sample CSS that fixes it, and now it makes sense, more...

#houseMenuH iframe {

position: absolute;

left: 0;

top: 0;

z-index: 0;

filter: progid:DXImageTransform.Microsoft.Alpha(style=0,opacity=0);

display: block;

}

I'll leave the sample up on my site though for any who are still intrested in answering the "why" :->

 

 


Josh Martin

 
New Post
2/1/2008 1:33 AM
 

HI

I cant tell you yet about the css but the ifrme is a standard trick that people use for this kind of menu. This will prevent objects like flash banners and from elements to appear above your menu. Normally with ul li and pure css in ie all flash objects and form elements will be on top op your layers and that might make navigation hard therefore iframe are automatically injected so the always appear on top of other elements

as for css menu you could always try snapsis menu it has more posibillities to define the html output of the skinobejct

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Understanding unordered list behavoir and House MenuUnderstanding unordered list behavoir and House Menu


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out