/******************************************************************************* * BASIC LAYOUT MECHANICS * * GENERAL NOTES * - yes, that's a lot of DIVs for a three-column layout. there is a reason * it all. first, all the columns must be floated to prevent a 3-pixel text * jog (a bug) that IE/Win 6 and earlier have. I can't use CSS hacks around * this one and need the extra markup. But using all floats can have * positive consequences, especially when using floated elements that need * to be cleared, but without clearing the other columns of the layout. * - NEGATIVE MARGINS is an approach to the three-column CSS layout that seems * to have the most compatibility and potential. the real strength of this * idea is to have the ability to provide different colors (or images) as * the background for each column. traditional three-column layouts can't * do this because the columns are only as tall as needed to fit their * content. in other words they don't run the full height of the layout. * negative margins gives us a means to fake this functionality. borders * (or padding, or margins) applied on #outer-column-container reserve the * space where the left and right columns will live. all three columns are * floated. since the columns are cleared inside #inner-column-container, * #inner-column-container (and #outer-column-container) will be as tall as * the tallest of the three columns. this means the borders will also be * this tall, giving the visual appearance that all three columns are the * same height. * - Some browsers, most notably older versions of Gecko (Netscape 7, FF 1.5 * & earlier) have a problem with this approach where the two side columns * won't be cleared if they exist entirely outside the space of the parent * element (#inner-column-container) where we clear the three columns. So * they need to be made to overlap the area of the middle column by at * least 1 pixels. This is why the outer columns have a 1 pixel margin on * their inner edge and the middle column (and source-order-container) * have negative margins (to make room for the 1px margin from the outer * columns). These negative margins should be moved into the HACKS section * in a future update. * * #page-container * - wraps the entire page. use this to set min/max widths and set any margins * or border that wraps the whole layout. * * #outer-column-container * - reserves space for the left and right columns. using borders allows you * to use the border color to act as the background color for the left and * right columns. background color could then act as the background of the * middle column. * * #inner-column-container * - provides the single-pixel black border between the middle column and * its outside brothers. * * #source-order-container * - source ordered layouts place the main content at the top of the page. to * do this with CSS in a three-column layout you need to wrap two of the * three columns in an element (DIV) to float them together as if it was a * a single column. * - this element contains both the #middle-column and #left-column elements. * * #middle-column, #left-column, #right-column * - containers for the each of the three columns in the layout * * #footer * - bottom of your webpage. a place to put copyright and contact information * * .clear-columns * - this class is assigned to an empty div placed after the last (floating) * column inside a block that contains two or more floating columns. it * clears the floats, forcing the element containing the columns to * visually contain all of its columns. there are alternative approaches * to clearing which do not require this extra markup (see * http://www.positioniseverything.net/easyclearing.html) however I find * this method is much more effective and compatible for the task at hand. * also, it should be evident by now that markup bloat is not a concern * with this particular layout. */ .clear-columns { clear: both; } #LogIn { position: absolute; /*padding-top: 10px;*/ padding-left: 2px; padding-right: 4px; /*top: 186px;*/ left: 620px;/*645*/ width: 200px;/*155*/ height: 87px; /*background-image: url(images/login.png); background-repeat: no-repeat;*/ color: #000; font-weight: bold; } .MyView, .MyView td { border-color: #c7c7c7; } #outer-column-container { border-left: solid 13em #fff; /* left column's width and background color */ border-right: solid 13em #fff; /* right column's width and background color */ } #menuBlock { width: 800px; height: 20px; margin-top: -3px; padding-top: 1px; background-image: url(images/menu.jpg); } #inner-column-container { width: 100%; /* force this element to take the full width between the left and right columns. this is especially important as children of this element will have width:100%; set, and how that 100% value is interpreted depends on the width of it's parent (this element). */ } #source-order-container { float: left; /* float left so the right column, which is outside this element, has a place to go. */ width: 100%; /* force this to go as wide as possible */ margin-right: -1px; /* make room for the right-column's overlap. */ } #left-column { float: left; /* float left, where it'll live */ margin-left: -13em; /* move it further left. the value here should be the same value as the left border width on #outer-column-container, but negative */ width: 13em; /* need to set a definite width, should be the same width as the left border width on #outer-column-container */ margin-right: 1px; /* overlap the middle column to help with clearing. see general notes above. */ } #middle-column { float: right; /* middle column goes right of the left column since the two share the same parent element */ width: 100%; /* make the middle column as wide as possible for a fluid layout. this is not possible if it's parent element, #source-order-container, wasn't also at 100% width */ margin-left: -1px; /* make room for the left-column's overflap */ } #right-column { float: right; /* float on the right side of the layout */ margin-right: -379px; /* move it further right. the value here should be the same value as the right border width on #outer-column-container, but negative */ width: 379px; /* need to set a definite width, should be the same width as the right border width on #outer-column-container */ margin-left: 1px; /* overlap the middle column */ } /******************************************************************************* * BASE THEME * * Setup basic styling for the layout. This will set gutterspace and generate a * basic border structure for the layout. Real layout styling belongs in a * separate "theme" stylesheet; leave this stylesheet untouched. */ body { background-color: #665; color: #000; padding: 0; /* padding on the body element when javascript min-width is in use will create problems in IE/Win 6. */ /*margin: 14px 0;*/ margin: 0; /* horizontal margins belong on #page-container. vertical margins are not there as well due to small rendering issues in IE/Win 5 when viewport is shorter than webpage */ } #page-container { background-color: #fff; /* background for the middle column */ border: solid 1px #fff; /* border around the entire layout */ width: 800px; /*min-width: 600px; limit how narrow the layout will shrink before it stops. */ margin: 0px; /*margin: 0 14px; horizontal margins here instead of on the body because we're setting min- width on this element. if margins set on body users will see an odd skip in the layout's rendering as it's resized below min-width. (JS-based min-width only.) */ } #masthead { height: 273px; padding-top: 0px; /* USE TO BE 1PX hack to force teh entire masthead to receive the background color */ border-bottom: solid 1px #fff; /* three of the four sides of this block will already have borders courtesy of the #page-container element so we only need to render the bottom. */ } #inner-column-container { border: solid 1px #fff; border-width: 0 1px; margin: 0 -1px; /* compensate for the borders because of 100% width declaration */ } #middle-column div.rMenu-center { border-bottom: solid 1px #fff; /* border along the bottom of the horizontal menu at the top of the middle column */ } #cssPageTitle { background-image: url(images/pageTitle.jpg); width: 379px; height: 77px; } #sectionImage { /*background-image: url(images/sectionImagen.jpg);*/ width: 379px; height: 311px; } #footer { border-top: solid 1px #fff; /* same situation as the masthead but this time we're rendering the top border. */ padding-bottom: 1px; /* hack to force the entire footer to receive the background color */ } .inside { margin: 10px; /* margin, instead of padding, used to induce margin collapse if needed by child elements */ } /******************************************************************************* * HACKS * * Not all browsers are created equal. Many CSS engines behave differently * and can create discrepencies in the rendering of your layout across different * browsing platforms. These hacks are aimed to resolve those discrepencies * and provide a more consistent look to the layout. * * CSS hacks work by playing to a bug in the CSS engine or parser for a given * browser. This forces the browser to either apply or ignore a rule that other * browsers wouldn't. This lets you apply rules to work around bugs in a specific * browser that would otherwise break the layout. * * It's important that when you use a CSS hack you do so in a way that is as * specific in targeting the problem browser as possible. Some hacks might * work for two or three different platforms, but you only need to apply it on * one platform. You might find that this hack has no adverse effects on those * other two platforms right now, but in a later version the hack might create * problems. Save yourself the headache and do as much as you can to narrow * the target of a CSS hack as much as possible. * * COMMON HACKS USED HERE * * The star-html hack (* html) targets Internet Explorer, both Windows and Mac, * for versions 6 and earlier. There is no element higher up in the page * than the HTML element. IE seems to think otherwise. Rules applied to any * selector that begins with "* html" will be ignored by just about every * browser except Internet Explorer. So any selector given below that begins * with "* html" is targetted at Internet Explorer. * * The backslash-star comment hack targets IE/Mac. CSS comments end with an * asterisk and forward slash. Anything after that closing comment mark will * be interpreted as as CSS rule. However if you prefix that closing comment * mark with a backslash, IE/Mac won't recognize that the comment has been * closed, but other browsers will. So any rules that come after the hacked * closing comment will be applied by any browser except IE/Mac until a * non-hacked closing comment is found. * * With the above two hacks outlined, it's possible to target IE on a specific * OS platform. This is important as the CSS and rendering engines for Mac and * Windows are completely different and have very different requirements in * terms of hacks. * * You may see other empty comments in wierd places, those are variations on * another comment hack to help target specific version of IE/Win (separating * IE 5 from IE6 typically). * * One other you'll see is a height setting of 0.1%. This is to trigger * hasLayout (see reference section below). IE (at least pre-version 7) * will automatically expand a box beyond it's set height if its content * is too tall. Setting height to 100% also works, but this can lead to * problems where an element that should only be a few pixels tall turns * out to be as tall as the rest of the page. By setting it to 0.1% you * minimize the chance of elements being set taller than they need to be. * * WHY USE HACKS? * * For compatibility sake. Specifics on what each hack does, and why its * used, is provided with the rule or ruleset in question. However, the * majority of hacks used have to do with an internal property in IE * called hasLayout. The first item in the reference section below has * all you could ever want to know, and more, about hasLayout. * * REFERENCE * http://www.satzansatz.de/cssd/onhavinglayout.html * http://www.communis.co.uk/dithered/css_filters/css_only/index.html */ .clear-columns { /* hide from IE/Mac \*/ padding-bottom: 1px; margin-bottom: -1px; /* this padding/margin hack is here for older Mozilla engines (Netscape 7, 6, FireFox pre 2.0) which will not allow an element to clear unless it has some effect on how the rest of the layout renders (ie, it takes up space). Hidden from IE/Mac as it triggers a horizontal scrollbar. */ } * html #page-container { /* \*/ height: 0.1%; /* IE/Win 5 needs this to prevent rendering issues if a minimum width is applied to this element and the viewport is sized narrower than it's minimum width. however this breaks IE/Mac so a comment hack is used to hide it. */ position: relative; /* IE/Mac 5.0 seems to need this. without it any child element with position: relative isn't rendered. */ } * html #middle-column, * html #left-column, * html #right-column, * html #source-order-container { /* hide from IE/Mac \*/ overflow: visible; /* a bug through IE/Win 6 causes the widths of text boxes to be calculated narrower than they render, causing overflow of their parent elements. we need to explicitly handle this overflow. IE/Win 5.0 does not handle visible overflow correctly and so on some layouts, at some viewport widths you'll get a horizontal scroll bar. */ /* hide from IE/Mac \*/ position: relative; /* this resolves rendering bugs in IE/Win. without this the columns don't render on screen or text jog. */ } * html #middle-column { margin-right: -4px; /* fix 3-pixel text jog in IE/Win 5.0. -4px because we also have to compensate for the overlaps from the left and right columns */ margin-right/* */: 0; /* reset value on 5.5 and later using comment hack to hide this rule from 5.0 */ } * html #middle-column .inside { margin-right: 14px; /* compensate for negative margin in previous rule */ margin-right:/* */: 10px; /* reset margins for 5.5 and later */ } * html #masthead, * html #footer { /* hide from IE/Mac \*/ height: 0.1%; /* this is to fix an IE 5.0 bug. setting this value forces these elements to contain their child elements, meaning margins will no longer collapse. */ height/**/: auto; /* reset for IE/Win 5.5 and later by hiding this rule from 5.0 with the empty comment hack. also hidden from IE/Mac for the same reason. */ } * html #masthead .inside, * html #footer .inside { margin-top: 0; margin-bottom: 0; /* since margins no longer collapse due to previous rules we remove vertical margins from the .inside class */ margin/* */: 10px; /* reset for IE 5.5 and later */ } * html .inside { margin: 10px 0.75em; /* i don't yet understand this bug in IE 5.0 which forces the right column down if the side margins are at a very specific value. if your side column widths are set in EMs, 0.75em seems to work fine. */ margin/* */: 10px; /* reset for IE 5.5 and later */ } * html #inner-column-container { display: block; } * html #source-order-container { margin-right: -100%; /* IE/Mac will force #source-order-container to the width of #left-column, even though that element is no longer inside it. this negative margin will help IE/Mac keep the three columns together under narrower viewports than normal. /* \*/ margin-right: -1px; /* reset the above hack for IE/Win */ } #left-column, #right-column { position: relative; /* resolve issues with links in left and right columns not being clickable in Safari */ } /******************************************************************************/ /******************************************************************************* * skidoo_redux_theme.css : 2007.03.05 : ruthsarian@gmail.com * ----------------------------------------------------------------------------- * * This stylesheet provides the theme of the layout. The theme includes * anything that controls the presentation of the page, but typically it's just * for setting colors, fonts, borders, and gutter space. * * It is possible to offer multiple themes for a single page and allow the * user to pick the one that best fits their needs. * * ------------------------------------------------------------------------------ * This stylesheet is released into the public domain. *******************************************************************************/ #page-container { font-size: 80%; /* font attributes set here so that the font sizer javascript bit can operate on the body element and not fubar things */ font-family: arial, helvetica, sans-serif; } #page-container, #inner-column-container, #masthead, #footer { border-color: #fff; /* all the borders within the layout */ } #outer-column-container { border-left-color: #f6f6f6; /* left column background */ border-right-color: #e6e6e6; /* right column background */ } #masthead { background-color: #f6f6f6; /* masthead background color */ } #footer { background-color: #a1adae; /* footer background color */ color: #fff; font-size: 11px; text-align: center; background-image: url("images/footer.jpg"); background-repeat: repeat; background-position: 100% 0; } #inner-column-container { background-color: #fcfcfc; /* middle column background */ } #left-column h3, #right-column h3 { margin-bottom: 0; /* column menu titles should hug the menus */ } #right-column p, #right-column ul { margin-top: 0; } .titleTxt { padding-top: 15px; font: arial; font-size: 25px; color: #fff; font-weight: bold; vertical-align: middle; text-align: center; } .mainMenu { font-size: 11px; font-weight: bold; font-family: Arial; } .menuStatic { color: #ffffff; } .menuHover { color: Orange; } p.fontsize-set { text-align: center; /* center the icons for changing font size */ } p.fontsize-set input { margin: 0 2px; /* space them out a bit */ } .galleryTitle { font-size: 12px; color: #00932d; font-weight: bold; } .redTitle { font-size: 12px; color: #800101; font-weight: bold; padding: 5px; } .pageTitle { font-size: 13px; font-family: Arial; color: #f89904; font-weight: bold; padding-left: 10px; } /******************************************************************************* * RMENU RELATED STYLES * * These are styles specifically for the menus used in the layout. This has its * own section because there are quite a lot of rules that need to be set * in order to control just the theme of the menu. * */ ul.rMenu li { background-color: #fcfcfc; /* background of menu items */ } ul.rMenu li:hover, ul.rMenu li.sfhover { background-color: #ddf; /* background color of parent menu item when mouse is over a submenu */ } ul.rMenu li a, #middle-column div.rMenu-center { border-color: #99a; /* border color of menu items */ } ul.rMenu li a:hover { color: #fff; /* color of menu item when mouse is over it */ background-color: #99f; /* background color of menu item when mouse is over it */ } ul.rMenu li.sfhover a:active, ul.rMenu li:hover a:active { color: #fff; /* color of menu item when clicked */ background-color: #c00; /* background color of menu item when clicked */ } div.rMenu-center ul.rMenu li { background-color: #f6f6f6; /* horizontal menu background color */ } div.rMenu-center ul.rMenu li:hover, div.rMenu-center ul.rMenu li.sfhover { background-color: #ddf; /* background color of parent menu item when mouse is over a submenu of the horizontal menu */ } /******************************************************************************/ @charset "UTF-8"; /******************************************************************************* * rMenu.css : 2008.04.11 : ruthsarian@gmail.com * ------------------------------------------------------------------------------ * Ruthsarian Menus - A CSS-based dropdown menu system * * * * KNOWN BUGS * - Opera 7.23 and earlier have problems with absolutely positioned * elements positioned relative to a parent element. this causes a * problem with right-aligned horizontal menus. stay away from those * types of menus if you've got any reason to care about Opera 7.23 or * earlier versions. * * DEV NOTES * - setting position: relative; to ul.rMenu triggers a bug in Netscape 7 * and earlier that makes content jump as menus pop * - need to remember that when assigning multiple classes to an element * to list them left-to-right from most-specific to least-specific. * Otherwise IE/Mac flips out * - IE/Mac needs whitespace before tags in the markup * otherwise very odd things can happen * - hasLayout should not be triggered on LI elements under IE7 * - IE/Mac has a selector bug where rMenu-v* and rMenu-h* rules * are applied to rMenu-v and rMenu-h elements. ie rMenu-vRight rules * get applied to rMenu-v elements. This is incorrect. * - if any parent element of the menu is a float it (or the parent of * the menu) needs to be relatively positioned. Otherwise the menu * is not rendered on the page. * - z-indexing is all screwed up when you specify one menu's li * elements background color ( div.rMenu-center ul.rMenu li ) * under IE/7. I don't know why. IE/7 sucks. * * EXAMPLE HTML * * * ------------------------------------------------------------------------------ * This stylesheet is released into the public domain. *******************************************************************************/ /******************************************************************************* * General Menu Mechanics * * Below is a set of rules which is applicable to any list used within * this dropdown menu system. You could apply just these rules and get * a basic dropdown menu system working just fine in FireFox, Opera, * Safari, and most other modern browsers. */ ul.rMenu, ul.rMenu ul, ul.rMenu li, ul.rMenu a { display: block; /* make these objects blocks so they're easier to deal with */ margin: 0; padding: 0; /* get rid of padding/margin values that these elements may have by default */ } ul.rMenu, ul.rMenu li, ul.rMenu ul { list-style: none; /* proper browsers don't require this because block elements (see previous rule set) cannot take any list-style property. meaning existing list-style properties are removed when they are set to display: block. IE7 seems to ignore this fact under certain situations so we explicitly set it here even though it's, technically, incorrect CSS (but it will validate). */ } ul.rMenu ul { display: none; /* hide the sub-menus until needed */ } ul.rMenu li { position: relative; /* so sub-menus position relative to their parent LI element */ z-index: 1; } ul.rMenu li:hover { z-index: 999; /* make sure this and any sub-menus that pop appear above everything else on the page */ } ul.rMenu li:hover > ul/* hide from IE5.0 because it gets confused by this selector */ { display: block; /* show the sub-menu */ position: absolute; /* remove the sub-menus from the flow of the layout so when they pop they don't cause any disfiguration of the layout. NOTE: this value use to belong to the "ul.rMenu ul" selector, however it was discovered that IE7 will muck up z-indexing on the ULs under very specific conditions unless the position attribute is set ONLY as they pop and not at all times. the specific condition? setting a background color on LI elements using a selector other than "ul.rMenu li". I have no idea why this is the case, but it is. Also worth noting there's another fix for this bug. Simply set background-position: 0 0 on the ul.rMenu li:hover class selector. The idea is that IE7 needs an extra rule to give it something to do, to give it a reason to notice the element when it's display state changes. Just odd. */ } /******************************************************************************* * Extended Menu Mechanics * * These rules exist only for specific menu types, such as horizontal or * vertical menus, right or left aligned menus. */ ul.rMenu-hor li { float: left; width: auto; } ul.rMenu-hRight li { float: right; /* horizontal, right menus need their LI elements floated to get them over there */ } ul.rMenu-ver li { float: none; /* clear this so vertical sub-menus that are children of horizontal menus won't have their LI widths set to auto. */ } ul.rMenu-ver, ul.rMenu-ver ul { width: 10em; /* sub-menus need a defined width, especially vertical sub-menus. salt to taste. */ } ul.rMenu-wide { width: 100%; /* apply this rule if you want the top-level menu to go as wide as possible. this is something you might want if your top-level is a vertical menu that spans the width of a column which has its width pre-defined. IE/Win 5 seems to prefer a value of 100% over auto. */ } ul.rMenu-vRight { float: right; /* use this to float a vertical menu right. */ } ul.rMenu-lFloat { float: left; /* use this to float a vertical menu left. */ } ul.rMenu-noFloat { float: none; /* this is to cover those cases where a menu is floated by default and you have a reason to not float it. such as a menu on the right side of the screen that you want to have drops going left but not floated. to be honest, i don't think this rule is needed. the clearfix hack will resolve renering issues associated with a floated menu anyways. */ } /******************************************************************************* * Extended Menu Mechanics - Center Horizontal Menu * * This has it's own section to explain the unique nature of this feature. * * In the past center horiztonal menus were achieved by setting list items * to inline elements and then setting text-align to center. However these * inline list items could not properly anchor their child menus, instead * they would drop relative to the parent unordered list, not the list item. * * This means the only way to have drop menus from a center-aligned horizontal * menu is to somehow keep the list items as blocks. This makes use of * text-align impossible. Instead we must resort to CSS trickery to create * the illusion of a center-aligned list. * * The trick is simple enough. Push the menu right 50% of the available width, * and then pull it left 50% of the horizontal menu's width. However it's not * as simple as a couple position statements. When a rule is set with a value * of 50% you should be asking yourself "50% of what?". * * In terms of space, percent values are based on the dimensions of the parent * object. So if I set an element to a width of 50%, it will be 50% the width * of it's parent object. * * So move the UL element right 50% using positioning, then move the LI elements * for the first tier left 50% and we're good, right? * * Wrong! The UL element is a block element and takes 100% the width of its * parent element by default. This means left 50% on the LI elements puts them * right back where they were, as if we didn't move them at all. The trick is * to find a way to make the UL element collapse so that it takes on the width * of the horizontal menu and not the width of its parent. We can do this * easily enough by floating the UL element. * * With the UL element floated, we can position it right 50% and then position * the LI elements left 50% and we wind up with a perfectly centered horizontal * menu. * * There is one catch: we need to wrap this horizontal menu in an extra DIV * element and apply the clearfix class to it. If we don't clear the horizontal * menu with clearfix then the menu will act like a float (since we're floating * the UL element now) and content will start to the right of the menu. * * The parent DIV also allows us a place to add a border or padding for extra * visual treatment. That is why, in the CSS below, there is a parent * div.rMenu-center element specifically referenced. * * The added HTML for your menu would be: * *
* ...{ your regular menu here }... *
* * NOTE: IE/Macs won't center these, they will display as left-aligned. This is * something that needs to be worked on. * * IE has problems with z-indexing on elements with hasLayout set. Most * menus don't have hasLayout set except on the LIs. These centered * menus have hasLayout set on the top-level UL. This breaks z-indexing. * Do not stack this menu anywhere near other menus or they will * overlap incorrectly. The only fix for this is to specificly set * z-index values where the top-most menu (first in the page) has * the highest z-index with the values decreased the farther down * the page you go. */ div.rMenu-center ul.rMenu { float: left; position: relative; left: 50%; } div.rMenu-center ul.rMenu li { position: relative; left: -50%; } div.rMenu-center ul.rMenu li li { left: auto; } /******************************************************************************* * DROP POSITIONS * * This handles where sub-menus drops relative to the parent element. The same * attributes should be set in all rule sets in this section so that cascading * rules don't create problems. * * NOTE: The suckerfish/form fields hack found towards the bottom of this * stylesheet overwrites a few of these rules for IE 6 and earlier. If * you change any of the LEFT attributes here you need to also make the * same changes to the * html rule set down below. */ ul.rMenu-hor ul { top: auto; /* a value of 100% creates a problem in IE 5.0 and Opera 7.23 */ right: auto; left: auto; /* typically want a value of 0 here but set to auto for same reasons detailed above */ margin-top: -1px; /* so the top border of the dropdown menu overlaps the bottom border of its parent horizontal menu. */ } ul.rMenu-ver ul { left: 60%; right: auto; top: auto; margin-top: -0.5em; /* i prefer top: 80% but this creates a problem in iCab so negative top margin must be used. salt to taste. */ } ul.rMenu-vRight ul, ul.rMenu-hRight ul.rMenu-ver ul { left: -60%; right: auto; top: auto; margin-top: -0.5em; /* i prefer top: 80% but this creates a problem in iCab so negative top margin must be used. salt to taste. */ } ul.rMenu-hRight ul { left: auto; right: 0; /* this doesn't work in Opera 7.23 but 7.5 and beyond work fine. this means right-aligned horizontal menus break in Opera 7.23 and earlier. no workaround has been found. */ top: auto; margin-top: -1px; /* so the top border of the dropdown menu overlaps the bottom border of its parent horizontal menu. */ } /******************************************************************************* * PRESENTATION : General * * This is where the visual presentation of the menu is handled. If you try to * alter the borders width or location of placement pay close attention to the * notes provided with the existing CSS rules in this section. There are key * reasons behind borders and negative margins being placed where they are. */ ul.rMenu li a { border: solid 1px #99f /* border around all anchor tags */ } ul.rMenu-hor li { margin-bottom: -1px; /* this is so if we apply a bottom border to the UL element it will render behind, but inline with the bottom border of the LI elements. */ margin-left: -1px; /* negative borders on LIs to make borders on child A elements overlap. they go here and not on the A element for compatibility reasons (IE6 and earlier) */ } ul.rMenu-hor { padding-left: 1px ; /* compensate for the 1px left jog created by the above negative margin. */ } ul.rMenu-ver li { margin-left: 0; margin-top: -1px; /* same thing above except for vertical menus */ } ul.rMenu-ver { border-top: solid 1px #fff; /* ditto */ } ul.rMenu li a { padding: 2px 5px 3px; /* 2px top, 3px bottom always seems to provide the most visually balanced padding */ } ul.rMenu li a:link, ul.rMenu li a:hover, ul.rMenu li a:visited, ul.rMenu li a:active { text-decoration: none; } ul.rMenu li.sfhover a:active, ul.rMenu li:hover a:active { color: #fff; background-color: #c00; } ul.rMenu li { background-color: #ddf; /* default background color of menu items */ } ul.rMenu li:hover, ul.rMenu li.sfhover { background-color: #eda; /* background color for parent menu items of the current sub-menu. includes the sfhover class which is used in the suckerfish hack detailed later in this stylesheet. */ } ul.rMenu li a:hover { background-color: #ffc; } /******************************************************************************* * PRESENTATION : Expand * * the bits below implement a graphic to appear on those anchor elements which * have the rMenu-expand class assigned. this is something you have to do * manually on any LI element containing a UL element that is to be a dropdown * menu. there is no mechanism to do this automatically. * * the seemingly redundant CSS is done for reasons similar to the suckerfish * css. it's to deal with all sorts of nested menu issues. it'll work as far * as three levels deep, after that all bets off. */ ul.rMenu li.rMenu-expand a, ul.rMenu li.rMenu-expand li.rMenu-expand a, ul.rMenu li.rMenu-expand li.rMenu-expand li.rMenu-expand a { padding-right: 25px; background-image: url("expand-right.gif"); background-repeat: no-repeat; background-position: 100% 50%; } ul.rMenu-vRight li.rMenu-expand a, ul.rMenu-vRight li.rMenu-expand li.rMenu-expand a, ul.rMenu-vRight li.rMenu-expand li.rMenu-expand li.rMenu-expand a, ul.rMenu-hRight li.rMenu-expand a, ul.rMenu-hRight li.rMenu-expand li.rMenu-expand a, ul.rMenu-hRight li.rMenu-expand li.rMenu-expand li.rMenu-expand a { padding-right: 5px; padding-left: 20px; background-image: url("expand-left.gif"); background-repeat: no-repeat; background-position: -5px 50%; } ul.rMenu-hor li.rMenu-expand a { padding-left: 5px; /* reset padding */ padding-right: 15px; background-image: url("expand-down.gif"); background-position: 100% 50%; } ul.rMenu li.rMenu-expand li a, ul.rMenu li.rMenu-expand li.rMenu-expand li a, ul.rMenu li.rMenu-expand li.rMenu-expand li.rMenu-expand li a { background-image: none; padding-right: 5px; /* reset padding */ padding-left: 5px; /* reset padding */ } /******************************************************************************* * HACKS : General * * These are rules specifically targeted to resolve bugs/quirks that some * browser exhibit. * * REFERENCES: * http://www.webdevout.net/css-hacks * http://www.satzansatz.de/cssd/onhavinglayout.html * http://www.communis.co.uk/dithered/css_filters/css_only/index.html */ * html ul.rMenu { display: inline-block; /* this is for IE/Mac. it forces IE/Mac to expand the element's dimensions to contain its floating child elements without a clearing element. */ /* \*/ display: block; /* override above rule for every other browser using IE/Mac backslash hack */ position: relative; /* IE 5.0/Mac needs this or it may clip the dropdown menus */ /* \*/ position: static;/* reset position attribute for IE/Win as it causes z-index problems */ } * html ul.rMenu ul { float: left; /* IE/Mac 5.0 needs this, otherwise hidden menus are not completely removed from the flow of the document. */ /* \*/ float: none; /* reset the rule for non-Macs */ } ul.rMenu ul { background-color: #fff; /* IE/Win (including 7) needs this on an object that hasLayout so that it doesn't "look through" the menu and let any object (text) below the menu to gain focus, causing the menu to disappear. application of this rule does not cause any rendering problems with other browsers as the background color his covered by the menu itself. */ } * html ul.rMenu-ver li, * html ul.rMenu-hor li ul.rMenu-ver li { /* the second selector above is there because of problems IE/Mac has with inheritance and what rules should take precedence. and to serve as a reminder on how to work around the issue if it's encountered again down the road. */ width: 100%; float: left; clear: left; /* IE likes to stick space below any LI in :hover state with a sub-menu. floating the LIs seems to work around this issue. But note that this also triggers hasLayout because we need a width of 100% on floats. */ } *:first-child+html ul.rMenu-ver > li/* hide from IE5.0 because it gets confused by this selector */ { width: 100%; float: left; clear: left; /* same as previous rule set except this is for IE7 and the direct child selector make inheritence much easier and obvious */ } ul.rMenu li a { position: relative; /* trigger hasLayout for IE on anchor elements. without hasLayout on anchors they would not expand the full width of the menu. this rule may not trigger hasLayour in later versions of IE and if you find this system broken in new versions of IE, this is probably the source. */ min-width: 0; /* triggers hasLayout for IE 7 */ } * html ul.rMenu-hor li { width: 6em; /* IE Mac doesn't do auto widths so specify a width for the sake of IE/Mac. Salt to taste. */ /* \*/ width: auto; /* now undo previous rule for non Macs by using the IE Mac backslash comment hack */ } * html div.rMenu-center { position: relative; z-index: 1; /* IE 6 and earlier need a little help with z-indexes on centered menus */ } html/* */:not([lang*=""]) div.rMenu-center ul.rMenu li a:hover { height: 100%; /* for Netscape 6 */ } html:/* */not([lang*=""]) div.rMenu-center ul.rMenu li a:hover { height: auto; /* reset for Netscape 7 and better */ } /******************************************************************************* * HACKS : Suckerfish w/Form Field Support (for IE 5.5 & 6.x) * * IE6 and earlier do not support the :hover pseudoclass and so javascript is * used to add the "sfhover" class of any LI element that the mouse is currently * over. This method is called suckerfish and you can read up on it at: * http://www.htmldog.com/articles/suckerfish/dropdowns/ * * One problem with this approach is IE6 and earlier versions have a bug where * form fields appear over the dropdown menus regardless of z-index values. * The fix is to generate and stick an IFRAME element under the dropdown menus * as they pop. The JavaScript used to do this requires that we hide menus off * to the side of the screen ( left: -100000px; ), but normal rMenu operation * is to hide menus with the DISPLAY property ( display: none; ). So also * included in the set of rules below are rules to overwrite this original * functionality of rMenu and utilize the LEFT property to move menus off- * screen until needed. Any other rules that use the LEFT property in the * normal rMenu system will also have to be ovewriten here as well. This * includes the dropdown positions. * * NOTE: this allows for support of dropdown menus up to 3 levels deep. if you * want to support greather menu depth you need to alter these selectors. * read the above mentioned website for more info on how to do that. * * The fix to get dropdowns to appear over form fields requires we * position menus off screen rather than simply hiding them with * display:none. So you might think we should not be using the display * property in the fields below. However we can because these display * properties are only being set when a parent LI is being hovered, so * the JavaScript used to operate on these LIs will already have the * dimensions they need before these display rules are activated. */ * html ul.rMenu ul { display: block; position: absolute; /* ovewrite original functionality of hiding element so we can hide these off screen */ } * html ul.rMenu ul, * html ul.rMenu-hor ul, * html ul.rMenu-ver ul, * html ul.rMenu-vRight ul, * html ul.rMenu-hRight ul.rMenu-ver ul, * html ul.rMenu-hRight ul { left: -10000px; /* move menus off screen. note we're ovewriting the dropdown position rules that use the LEFT property, thus all the selectors. */ } * html ul.rMenu li.sfhover { z-index: 999; /* not totally needed, but keep the menu that pops above all other elements within it's parent menu system */ } * html ul.rMenu li.sfhover ul { left: auto; /* pull the menus that were off-screen back onto the screen */ } * html ul.rMenu li.sfhover ul ul, * html ul.rMenu li.sfhover ul ul ul { display: none; /* IE/Suckerfish alternative for browsers that don't support :hover state on LI elements */ } * html ul.rMenu li.sfhover ul, * html ul.rMenu li li.sfhover ul, * html ul.rMenu li li li.sfhover ul { display: block; /* ^ ditto ^ */ } * html ul.rMenu-ver li.sfhover ul { left: 60%; /* dropdown positioning uses the left attribute for horizontal positioning. however we can't use this property until the menu is being displayed. note that all ULs beneath the menu item currently in the hover state will get this value through inheritance. however all sub- menus still won't display because two rule sets up we're setting the DISPLAY property to none. */ } * html ul.rMenu-vRight li.sfhover ul, * html ul.rMenu-hRight ul.rMenu-ver li.sfhover ul { left: -60%; /* ^ ditto ^ */ } * html ul.rMenu iframe { /* filter:progid:DXImageTransform.Microsoft.Alpha(style=0,opacity=0); */ /* the above rule is now applied in the javascript used to generate the IFRAME this is applied to. it allows the CSS to validate while keeping the original functionality. */ position: absolute; left: 0; top: 0; z-index: -1; /* this is the IFRAME that's placed behind dropdown menus so that form elements don't show through the menus. they are not set programatically via javascript because doing so generates some lag in the display of the dropdown menu. */ } /******************************************************************************* * HACKS : Clearfix * * Clearfix provides a means to for an element to contain all it's floated * children even if it's not normally tall enough to do so. For more information * on clearfix please see: * http://www.positioniseverything.net/easyclearing.html */ .clearfix:after { content: "."; display: block; height: 0; clear: both; visibility: hidden; } .clearfix { min-width: 0; /* trigger hasLayout for IE7 */ display: inline-block; /* \*/ display: block; /* Hide from IE Mac */ } * html .clearfix { /* \*/ height: 1%; /* Hide from IE Mac */ } /******************************************************************************/ /* ** DEMO CSS BEGINS ** */ /*this is used to take the left column away, but if I use a background image for the column then I CANNOT USE THIS CODE*/ #outer-column-container, #inner-column-container { border-right-width: 0; } #right-column { display: none; } #source-order-container { margin: 0; } /* ** DEMO CSS ENDS ** */ /* ** DEMO CSS BEGINS ** */ #outer-column-container { border-left-width: 0; border-right-width: 0; /* we remove the borders so we can apply background images. */ /*padding-left: 13em; because padding is on the left-side, the left-column"s background image is going to be applied to this element. */ margin-right: 0px; /* the right-column"s space is reserved with margin space rather than padding, so we can apply a background image to the parent element, #pageWrapper, and it will peek through. */ /*background-image: url("../images/banner.jpg");*//*left columsn*/ background-repeat: repeat; background-position: 0 0; } #page-container { background-image: url("../images/spanOrders1.jpg"); background-repeat:repeat-x; background-position: 100% 0; } /* #masthead { background-image: url("../images/tile21.jpg"); background-repeat: repeat; background-position: 100% 0; } #footer { background-image: url("images/menu.jpg"); background-repeat: repeat; background-position: 100% 0; } #inner-column-container { background-image: url("../images/tile04.jpg"); background-repeat: repeat; background-position: 100% 0; } */ /* ** DEMO CSS ENDS ** */