Font rendering problem... (FLash BUG)

Hi all, I have Flash instaled on two machines and both of them are having a problem when rendring flash text.
All text on flash appears like the image bellow. And When I export to SWF the text stays the same.
The font I'm using is Myriad Pro
I'm running Flash on iMac i3 3.06 with 4Gb and 256 Graphics display so that can't be the problem.
Anyone any ideas?
Thanks for the attention.
y

Hi,
i know this problem. It exists since the last os-x update.
Until now there ist no solution - only two workarounds.
a) reinstall osx and update only to an older version
b) sometimes it helps me to close flash, restart flash and publish again.
It seems only OTF Fonts make Problems. I know about problems with MyriadPro and DIN.
There is also a problem creating PDF Files with the OS-X internal "Print as PDF" function.
I hope there will be an update soon....
Stefan

Similar Messages

  • Flex 4.5/FP10.2 web app: Font rendering problem

    Heya,
    Upped a web app from Flex 4.0/4.1 to Flex 4.5 & fonts started to render really badly (blurry & 'stronger').
    They are embedded as CFF, no errors or warnings gives. Also upgraded to Flash Player 10.2, which apparently has 'enhanched' font rendering.
    Haven't set applicationDPI on the s:Application tag, so DPI management should be disabled according to the docs.
    (See http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c682e5a9412cf5976c17-8000.htm l)
    It's straight up @font-face embeds in a CSS file, nothing odd or wrong there.
    Is the case that this is how it's supposed to look now? In that case, how do I revert back to sane rendering?
    Do I need to configure 4.5 somehow to get it to do fonts right?

    Also tested Franklin Gothic, same deal. Tested on Mac (10.2) & PC (10.2 & 10.3). Flex 4.5 for both platforms.
    fonts.css:
    @font-face
    src: url("fonts/arial.ttf");
    font-family: Arial;
    font-weight: normal;
    embedAsCFF: true;
    FontTest.mxml:
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
       xmlns:s="library://ns.adobe.com/flex/spark"
       xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
    <fx:Style source="fonts.css"/>
    <s:Label x="20" y="20"
    fontFamily="Arial"
    fontLookup="embeddedCFF"
    fontSize="12"
    cffHinting="horizontalStem"
    text="TESTAR Testar testar" />
    </s:Application>

  • Mac os x font rendering problems 1680x1050 LCD

    Hello,
    I recently bought a Mac Mini and love it except I cannot tune the font rendering using command line "defaults -currentHost write -globalDomain AppleFontSmoothing -int 1" and using 0,1,2,3 to try out, restarting apps after each change.   It seems that "1" is the best setting for my ASUS  VW224U widescreen lcd display.   The fonts are blurry.   Is it that Mac OS X cannot work well with this 1680x1050 display resolution?  Anyone have good font display at this resolution?
    TIA

    I have the same problem.
    Changed my mac mini core 2 duo with snow leopard for a new mac mini core i5, radeon graphic card and, of course, Lion 10.6.1.
    I kept the same screen a dell U2410 connected on display port.
    The immediate result was absolutely awful.
    I had to change settings on my display :
    1 - the shaprness setting from 50 to 0 (on a scale from 0 to 100)
    2 - the color temperature, called preset mode, from Adobe RVB to standard
    Otherwise, the fonts were rendered  :
    1 - very harsh
    2 - with very visible subpixels to anti-alias
    But even with this new settings, the result is far from being good as it was just before...
    I have tried to change font smoothing parameters as you describe in your post but, if i see differences between 1 2 and 3, i found none optimal ... (and kept 2)
    I'm going mad !
    It could be better with a calibration of the screen (it seems everything is washed out...) but my colorimeter is not compatible with Lion  ...

  • Arial font rendering problem in Label control AIR

    Hi,
        I have a label in my application which is rendered with font-family Arial. The letters are not getting viewed properly.Some letters are cutted especially "W". I have attached a screen shot of it. Is it a bug in Adob Air.You can notice that letter "W" is cutted. Is it possible to fix it or not.Please help me.
    Regards,
    Jayagopal.

    One thing to add for clarification, the problem I described is the application display problem and NOT the screen capture problem.
    Yu-Ten Lee

  • Arial font rendering problem in AIR

    Hi,
        I am new to flex. I have a problem in rendering arial font in Label in AIR application.
    I have attached the screen shot.The letter W has been cutted.
    Regards,
    Jayagopal.

    OK, I eventualy discover that Java uses its own font configuration, and look for the fonts in /usr/share/fonts/TTF. As I use Bohoomil bundle fonts, which does not install fonts in this directory, Java wasn't finding the right fonts.
    Copying the DejaVu family in /usr/share/fonts/TTF solved the problem.

  • Diagnosing Arabic font rendering problem

    I have an application that is localized into Arabic. On three machines I have access to to test on (Windows Vista, OS X, and Fedora 9), when the locale is set to Arabic, the UI is rendered correctly - menus, buttons, etc. all have their text rendered in Arabic and look fine.
    The person that translated the text into Arabic, however, doesn't have the same results. He's running Linux (can't remember what flavor) and when he runs the application, the Arabic text all comes out as boxes. He says this is the case for any LookandFeel he tries (Metal that hideous GTK, Nimbus).
    Since I can verify that the application does look okay on some machines, I feel comfortable in thinking that it's an issue on his specific machine. My question is - how can we diagnose what the problem actually is?
    His machine's default locale is Arabic, and other (non-Java) applications render Arabic text fine.
    He's using Sun Java 1.6 (not sure what minor release though), not GNU Java.
    (Possibly?) relevant info:
    I noticed that several UI keys such as "Menu.font" and "Button.font" are using a Deja Vu font on my Vista system when rendering Arabic. He says his system does have Deja Vu fonts installed, but when he's getting his boxes displayed, it seems these properties are set to some other Bitstream Vera font.

    Sorry, I haven't a clue regarding a possible solution, but I thought I'd share this:
    BoBear2681 wrote:
    I noticed that several UI keys such as "Menu.font" and "Button.font" are using a Deja Vu font on my Vista system when rendering Arabic. He says his system does have Deja Vu fonts installed, but when he's getting his boxes displayed, it seems these properties are set to some other Bitstream Vera font.According to [this page|http://linux.wareseeker.com/Desktop-Environment/dejavu-fonts-2.19.zip/314962]
    The DejaVu fonts are a font family based on the Bitstream Vera Fonts
    db

  • Java fonts rendering problem

    Hi all,
    I've used JEditorPane to render an html page.
    My problem is that the way to interpreter fonts seems different from Java to the operating system font, also if I have the same font installed (for example Arial TT unicode).
    For example, I have an html page that misure 100 pixel with Explorer or similar; if I render it in Java, GetPreferredSize return me a value like 130, also if I've installed the same font and I have fixed the style of the page with css.
    In this a bug?
    --Carlo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Have you used getInstalledFonts to see if the font is actually available to java?
    Not all fonts on the system can be used (especially under Unix/Linux). In which case Java would use a different font as a substitute.
    MArkee

  • Chinese font rendering problem

    Firstly.. I have installed ttf-arphic-uming, ttf-arphic-ukai and ttf-fireflysung. Idon't really understand why most of characters have rendered except for that one. This happens very sporadically (but always the same ones).
    I do not have a clue why this is miscoloured like that.. I think this only occurs with chinese.
    Any help is appreciated.

    Manifold wrote:
    Firstly.. I have installed ttf-arphic-uming, ttf-arphic-ukai and ttf-fireflysung. Idon't really understand why most of characters have rendered except for that one. This happens very sporadically (but always the same ones).
    I do not have a clue why this is miscoloured like that.. I think this only occurs with chinese.
    Any help is appreciated.
    It's subpixeling. Maybe you specified the setting for this font somewhere?

  • [SOLVED] Bad font rendering after last update (pango issue?)

    I am getting very strange font rendering problem. Look at the screen below. It only affects gtk windows (as you can see below HTML text is currently displayed, but url bar and context menu is not). I belive it appeared after upgrading pango package to 1.32, but downgrading it as instructed here (https://bbs.archlinux.org/viewtopic.php?id=151886), didn't help. Does anybody know what can it be? Any hints where to look for the solution?
    Maciej
    Last edited by mamciek (2012-11-20 22:01:45)

    brebs wrote:https://bugs.archlinux.org/task/32612?project=1
    That seems to be an issue. Downgrading to  xorg-server 1.13.0-3 resolved problem. Watching ticket for future updates. Thanks a lot
    Last edited by mamciek (2012-11-20 22:02:58)

  • [SOLVED] Bad font rendering and overlapping since last update

    Hi all! Since the last updates I'm getting font rendering problems. I'm seeing something like this in lots of applications:
    See the "ce" in Facebook, those letters are kinda overlapped! This happens in Nautilus too, for example in the word "devel". I'm using the Ubuntu patches for font rendering, but actually I have problems even with the stock packages.
    I'm on a fresh install right now (I really needed to clean the old one, too much experimenting xD) and I keep having this problem.
    Can anyone help me?
    SOLVED I downgraded pango from 1.32.1-1 to 1.30.1-1 and everything went back to normality
    Last edited by Gianfrix (2012-11-06 14:09:00)

    brebs wrote:https://bugs.archlinux.org/task/32612?project=1
    That seems to be an issue. Downgrading to  xorg-server 1.13.0-3 resolved problem. Watching ticket for future updates. Thanks a lot
    Last edited by mamciek (2012-11-20 22:02:58)

  • Not-latin font rendering is broken in Kf5 applications

    Hello.
    After upgrading of KDE4 applications to Kf5 ones, I have the font rendering problem in them.
    It's looks like that:
    As you can see, rendering of cyrillic fonts is broken. Absolutely wrong font family (should be Terminus) and font size.
    In KDE4 apps font rendering works correctly.
    Do someone have any suggestions how can I fix this?

    I can see picture without any problems. May be it is regional-specific problem of image hosting.
    Google drive link: https://drive.google.com/file/d/0B-ZoDS … sp=sharing
    Last edited by Lampus (2015-02-03 13:27:56)

  • What can be done about the terrible font rendering in Adobe Flash 11.6?

    Some fonts in the latest version of Adobe Flash are terrible.  They are almost unreadable!
    Take a look at the fonts rendered from Adobe's own site:   (Can you read what version or OS or Browser?)
    I have other sites where the fonts are readable but they are still very bad.
    Please help!
    Mike

    I have found a solution. The problem is really with Google Chrome v 25.???  To get it to work properly you will need to go to    chrome://plugins/   and "enable" the pepflashplayer.dll.
    I had to click on the "+ Details" link on the far right, in the plugins header bar.  This will open a hidden portion to the Flash player and you can then enable that .dll.  It looks a bit like this:
    Name:
    Shockwave Flash
    Description:
    Shockwave Flash 11.6 r602
    Version:
    11.6.602.171
    Location:
    C:\Users\mrice\AppData\Local\Google\Chrome\Application\25.0.1364.97\PepperFlash\pepflashpl ayer.dll
    Type:
    PPAPI (out-of-process)
    Enable
    MIME types:
    MIME type
    Description
    File extensions
    application/x-shockwave-flash
    Shockwave Flash
    .swf
    application/futuresplash
    FutureSplash Player
    .spl
    This worked for me.
    I also posted this solution on the Google Chrome "feedback" page. 
    Good Luck,
    Mike

  • [NEARLY SOLVED] font rendering in gtk apps problem after last upgrade

    Im' using KDE, cairo-lcd, libxft-lcd... my fonts looked beautifully, but now they look horrible...
    After last upgrade my gtk apps (firefox, thunderbird) render fonts in an ugly way...
    I've tried to revert to pango 1.16.5 with no lucky result (the same problem)...
    here is the log:
    [2007-08-19 14:56] upgraded bind (9.4.1_P1-2 -> 9.4.1_P1-3)
    [2007-08-19 14:56] upgraded glib2 (2.14.0-2 -> 2.14.0-3)
    [2007-08-19 14:56] upgraded gnupg2 (2.0.5-1 -> 2.0.6-1)
    [2007-08-19 14:57] upgraded gtk2 (2.10.14-2 -> 2.10.14-3)
    [2007-08-19 14:57] upgraded kernel26ck (2.6.22.2.ck1-1 -> 2.6.22.3.ck1-1)
    [2007-08-19 14:57] upgraded libdownload (1.1-1 -> 1.1-2)
    [2007-08-19 14:57] upgraded libevent (1.3b-1 -> 1.3d-1)
    [2007-08-19 14:57] upgraded libxtst (1.0.2-1 -> 1.0.3-1)
    [2007-08-19 14:57] upgraded nvidia-ck (100.14.11-2 -> 100.14.11-3)
    [2007-08-19 14:57] upgraded sip (4.6-1 -> 4.7-1)
    [2007-08-19 14:57] upgraded pyqt (3.17.2-1 -> 3.17.3-1)
    [2007-08-19 14:57] upgraded xf86-input-joystick (1.2.2-1 -> 1.2.3-1)
    [2007-08-19 14:57] upgraded xorg-server-utils (1.0.4-1 -> 1.0.4-2)
    [2007-08-19 14:57] upgraded xorg-utils (1.0.2-2 -> 1.0.2-4)
    [2007-08-19 14:57] upgraded xorg-xdm (1.1.5-1 -> 1.1.6-1)
    [2007-08-19 14:57] upgraded xterm (225-1 -> 229-1)
    [2007-08-21 00:16] upgraded cpio (2.8-1 -> 2.9-1)
    [2007-08-21 00:16] upgraded ed (0.5-3 -> 0.8-1)
    [2007-08-21 00:16] upgraded initscripts (2007.08-1 -> 2007.08-2)
    [2007-08-21 00:16] upgraded intltool (0.36.0-1 -> 0.36.1-1)
    [2007-08-21 00:16] upgraded libarchive (2.2.5-1 -> 2.2.6-1)
    [2007-08-21 00:16] upgraded man-pages (2.60-1 -> 2.64-1)
    [2007-08-21 00:16] upgraded pciutils (2.2.4-2 -> 2.2.6-1)
    [2007-08-21 00:16] upgraded readline (5.2-2 -> 5.2-3)
    [2007-08-22 00:16] upgraded gdbm (1.8.3-3 -> 1.8.3-4)
    [2007-08-22 00:17] upgraded kernel26 (2.6.22.3-1 -> 2.6.22.4-2)
    [2007-08-22 00:17] upgraded lcms (1.16-1 -> 1.17-1)
    [2007-08-22 00:17] upgraded libice (1.0.2-1 -> 1.0.4-1)
    [2007-08-22 00:17] upgraded libxrender (0.9.2-1 -> 0.9.3-1)
    [2007-08-22 00:17] upgraded procinfo (18-3 -> 19-1)
    [2007-08-22 00:17] upgraded xorg-apps (1.0.2-4 -> 1.0.3-1)
    [2007-08-22 23:49] upgraded kernel26 (2.6.22.4-2 -> 2.6.22.4-2.1)
    [2007-08-22 23:49] upgraded librsvg (2.18.0-1 -> 2.18.1-1)
    [2007-08-22 23:49] upgraded libxpm (3.5.6-1 -> 3.5.7-1)
    [2007-08-22 23:49] upgraded libxaw (1.0.3-1 -> 1.0.4-1)
    [2007-08-22 23:49] upgraded makedev (3.8.3-1 -> 3.23-1)
    [2007-08-22 23:49] upgraded mcpp (2.6-1 -> 2.6.4-1)
    [2007-08-22 23:49] upgraded naim (0.11.8.2.1-1 -> 0.11.8.3.1-1)
    [2007-08-22 23:49] upgraded nfs-utils (1.0.12-2 -> 1.0.12-3)
    [2007-08-22 23:49] upgraded pam (0.81-4 -> 0.99.8.1-3.1)
    [2007-08-22 23:49] upgraded pango (1.16.5-1 -> 1.18.0-1)
    [2007-08-22 23:49] upgraded sox (13.0.0-1 -> 13.0.0-2)
    [2007-08-22 23:49] upgraded xorg-apps (1.0.3-1 -> 1.0.3-2)
    [2007-08-22 23:49] upgraded xtrans (1.0.3-1 -> 1.0.4-1)
    [2007-08-25 15:25] upgraded glibc (2.6.1-1 -> 2.6.1-2)
    [2007-08-25 15:25] upgraded bftpd (1.9-1 -> 2.0-1)
    [2007-08-25 15:25] upgraded gcc (4.2.1-3 -> 4.2.1-3.1)
    [2007-08-25 15:25] upgraded gtk-doc (1.8-2 -> 1.8-3)
    [2007-08-25 15:25] upgraded hal-info (0.20070618-1 -> 0.20070725-1)
    [2007-08-25 15:25] upgraded perl-xml-simple (2.16-2 -> 2.18-1)
    [2007-08-25 15:25] upgraded icon-naming-utils (0.8.2-2 -> 0.8.5-1)
    [2007-08-25 15:26] upgraded kernel26 (2.6.22.4-2.1 -> 2.6.22.5-1)
    [2007-08-25 15:27] upgraded kernel26ck (2.6.22.3.ck1-1 -> 2.6.22.5.ck1-1)
    [2007-08-25 15:27] upgraded libgnomeprint (2.18.0-1 -> 2.18.1-1)
    [2007-08-25 22:41] removed libgnomeprintui (2.18.0-1)
    [2007-08-25 22:41] removed libgnomeprint (2.18.1-1)
    i dunno what happened...
    plz, someone help me
    regards
    Last edited by saneone (2007-08-30 18:11:32)

    Bogart wrote:
    I think the spacing now is correct, while before it was wrong. The only "problem" is that you got used to a bad font rendering, and now that it has changed for better you feel like it's different and don't like it.
    Really, *most* of the problems that people find in Linux's fonts are just because they are used to the awful default fonts from Windows XP. Yes, people can even get used to those fonts and believe they're good!!! And when they see correct fonts in Linux they think they're bad...
    What I would do is remove the MS TTF fonts. They work bad in Windows and worse in Linux. You should use Bitstream Vera or DejaVu if you want good quality fonts (especially in web pages).
    But, then again, you might think that they look wrong just because you're not used to it... Oh, well...
    What does correct font / correct spacing mean ?
    IMO, that doesn't make any sense, because that's a totally subjective matter, like many other things in this world.
    BTW, I love how fonts look in Windows, and I think that must be the only thing MS got right. Thus, I'm using ms fonts in linux, and a rendering as close as possible (no autohinting or antialiasing or subpixel rendering).
    Similarly, I could find a woman beautiful that you would find ugly or just average. We are all different, and it's better that way

  • BUG: text rendering problems after keyboard firmware update

    Hey all!
    Just letting you know that today, after installing the keyboard/mouse firmware update 1.0, the font rendering in many applications become weird, letters may overlap, see some screenshots:
    http://artemio.net/tmp/apple/bug1.png
    http://artemio.net/tmp/apple/bug2.png
    My system is iMac Intel Core Duo 17", 2 GB RAM, 250 GB HDD, Mac OS 10.4.6.

    Just to clarify, that was a software update, not a firmware update. I don't think the keyboard has any resident firmware.
    Since this is a new update from Apple, and there have been very few posts about problems after it was installed, (I have seen a couple here) I think that you should call and speak directly with an Apple Customer Service rep. That way Apple knows some have issues with the update and they may have suggestions.
    Let us know what they say.

  • Spry Menu Bar 2.0 (1.0) - Handling of widget generated CSS, placement and rendering problems in CSS

    Hello:
    I wanted to repost my question to re-frame the issue based on what I have learned thus far.
    I am working on a website that has been developed using the Spry Menu Bar Framework UI (2.0) I.0, that has some peculiar rendering problems that affect IE 6 in particular.  The CSS is reprinted below.
    In particular, when I post the widget generated CSS in the head as it is orginally situated by the framework, the menu bar works fine.  However, it seemed to me that I should be able to reduce page weight (an important consideration considering my target population) by placing it in the general style sheet governing the entire site.
    When I place the styles at the beginning of the style sheet the menu doesn't render at all in any of the browsers (IE 6+, Firefox, Opera, Safari, Netscape, etc.) as it conflicts with the general rules governing links that appear later in the style sheet.  When I place the styles specific to the Menu bar at the end of the style sheet, then the menu bar renders properly in all browsers except IE 6.
    The odd thing is that the only way to ensure that the menu bar works in IE 6 is to keep the menu related styles in the head of each page.  This raises problems related to page weight (not an insurmountable consideration if no other solution can be found) but still an issue.  Likewise I need to support IE 6, again given the target audience/population.  The issue obviously has something to do with specificity, but I am not certain that is the only consideration at work here.  I have not tried the !important selector in regard to the menu, as IE 6 seems to only partially support this.
    Thanks in advance for any advice or insight that can be provided.  Thanks in particular to Martin for his contributions to my earlier question related to this issue.
    Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>
    The CSS governing the site generally is reproduced below:  (my belief is that it is the a:link, a:visited,  a:hover, a:active styles that may be in conflict).
    @charset "utf-8";
    body  {
        font: 100% Verdana, Arial, Helvetica, sans-serif;
       min-height: 0; /* This is necessary to overcome the "haslayout" bugthat is found in Windows 7 in conjuction with IE8.  For Moreinformation see: URL -- http://reference.sitepoint.com/css/haslayout.html */
        margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
        padding: 0;
        text-align:center; /* This allows for the centering of the container and overcomes a bug inherent in IE 5 */
        color: #000000;
        list-style-image: none;
        background-color: #FCFCFC;
    h1,h2,h3,h4,h5,h6 {
    color:#000066;
    a:link {
        color: #151A96;
        text-decoration: underline;
    a:visited {
        text-decoration: underline;
        color: #1B8DCD;
    a:hover {
        text-decoration: none;
        color: #F30A0A;
    a:active {
        text-decoration: underline;
        color: #151A96;
    #container {
        width: 960px;   
        margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
        text-align: left; /* this overrides the text-align: center on the body element. */
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Midsection %20_960.png);
        background-repeat: repeat-y;
    #header {
           padding: 0;  /* this padding matches the left alignment of the elementsin the divs that appear beneath it. If an image is used in the #headerinstead of text, you may want to remove the padding. */
            width:960px;
            height:332px;
            background-image:
            url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Header_960 .png);
            background-repeat:no-repeat;
    #header h1 {
        margin-right: 0px; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
        padding: 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
        display:none;
    #header img {
        display: none;
    #Main_nav_contents {
        padding: 0;
        margin-top: 0px;
        height: 39px;
        width: 950px;       
        padding-top: 275px; 
        padding-left: 39px;
        z-index: 3; 
    #MenuBarVertical {
        margin-bottom: 50px;
        padding-top: 50px;
        padding-bottom:200px;
        padding-left: 15px;
        padding-right: 15px;
    .mainContent_left {
       margin: 0;/* the right margin on this div element creates the columndown the right side of the page - no matter how much content thesidebar1 div contains, the column space will remain. You can removethis margin if you want the #mainContent div's text to fill the#sidebar1 space when the content in #sidebar1 ends. */
        padding-left:30px;
        padding-right:20px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
        width: 600px;
        float: left;
    .sidebar_right {
        float: right; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:0;
        margin-right:10px;
        font-size:90%;
    .mainContent_right {
        margin-left: 10px;
        padding-left:30px;
        padding-right:20px;
        width: 600px;
        float: right;
    .sidebar_left {
        float: left; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:30px;
        margin-right:0;
        overflow: hidden;
        font-size:90%;
    .main_content_centered {
        width: 650px;
        margin-left: 155px;
    .main_content_centered_header {
        margin-left: 75px;
    .sidebar_textbox {
        margin: 0px;   
        width: 260px;
        padding: 2px;
    .sidebar_textbox_header {
        width:255px;
        height:58px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Header.png);
    .sidebar_textbox_background_middle {
         width: 255px;   
        padding-top: 12px;   
        padding-bottom: 10px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Middle.png);
        background-repeat: repeat-y;
    .sidebar_textbox_content {
       /* The width and padding are set as follows to accomodate quirks inbrowser rendering and to ensure that text is contained within thebackground of the text box */
        width: 230px;
        padding-left: 20px;
        padding-right: 40px;
    .sidebar_textbox_footer {
        width:255px;
        height:64px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Port rait%20Textbox%20Footer.png);
    #issues_menu a:link {
        color: #151A96;
        text-decoration: none;
        font-weight:bold;
    #issues_menu a:visited {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #issues_menu a:hover {   
        color: #F30A0A;
        font-weight:bold;
        font-style: oblique;
        text-decoration: none;
    #issues_menu a:active {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #archives {
        padding-top: 15px;
        padding-right: 15px;
        padding-bottom: 20px;
        padding-left: 0px;
    .landscape_textbox {
        width: 500px;
        margin-right: 0px;
        margin-left: 30px;
        padding-top:35px;
        padding-bottom: 25px;
        font-style: normal;
        font-weight: normal;
    .landscape_textbox_hdr {
        width:500px;
        height:38px;
        margin:auto;
        padding:0;
        background-image:
    url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Landscape%20Textbox%2 0Header.png);
    .landscape_textbox_middle {
        width:auto;
        margin:auto;
        padding-top: 12px;
        padding-bottom: 12px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/lan dscapte%20Textbox%20Middle.png);
        background-repeat:repeat-y;
    .landscape_textbox_content {
        width:450px;
        padding:25px;
    .landscape_textbox_ftr {
        width:500px;
        height:44px;
        margin:auto;
        padding:0;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Lan dscape%20Textbox%20Footer.png);
    #footer {
        padding: 0; /* this padding matches the left alignment of the elements in the divs that appear above it. */
        width: 960px;
        height: 222px;
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Footer%20_ 960.png);
        background-repeat:no-repeat;
    #footer p {
       margin: 0px; /* zeroing the margins of the first element in the footerwill avoid the possibility of margin collapse - a space between divs */
        padding:0px; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
        text-align:center;
        margin-left: 50px;
        margin-right: 50px;
        padding: 10px;
        font-size: small;
    #footer h5 {
    text-align:center;
    .fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
        float: right;
        margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .dropcap {
        display: block;
        float: left;
        line-height: 80%;
        font-size: 250%;
        font-weight: bolder;
        color: #000066;   
        padding: .03em .1em 0 0;
    .red_arrows {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Arrow%20Large.png);    
    .blue_bullets {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Bullet%20Medium%20Fu ll.png);   
    .attention {
        color: #F30A0A;
        font-size:x-large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .attention_small {
        color: #F30A0A;
        font-size:large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .table {
        table-layout:fixed;
    .blue {
        color: #00F;
    #container .mainContent_left p .blue {
        color: #0303A0;

    Hi Nancy:
    The specific code that I am referring to is the CSS code governing the styling of the spry menu widget that only works in IE 6 if, and only if, it remains in the head of the web page.  If removed and placed in a stylesheet, the IE plugins fail to compensate for the IE 6 "gap" bug.  As I said, it doesn't make sense to me that, assuming specificity is addressed, that these can not be included in an external style sheet.  I am looking for a) an explanation why they must remain embedded in the web page; and 2) any means by which I might be able to export them.
    I will reproduce the specific css style (code) below:  it should also be visable through reveal source --
    Thanks again, Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>

Maybe you are looking for

  • Error while calling HTTPService

    i am getting  [RPC Fault faultString="HTTP request error" faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032"] error while trying to call a htttpservice. the

  • Contact names not showing in messages, only number

    nokia 6121  no names will show when ringing or recieving texts so I dont know who they are from etc, very frustrating, how do I change it to show the contact name not number? I cant find any settings to help me? thanks

  • Substitution Management - Profile description

    Hi, creating a substitution rule via UWL standard is working fine.  But what I need to know is how can I customize the "Create substitution rule" view? When I have poped up that view I can choose between different profiles (default ALL, disciplinary.

  • 2014 Golden Globe Winners

    Awards season is officially upon us as the 71st Golden Globe Awards have now come and gone. This year’s Golden Globe Awards was hosted by Tina Fey and Amy Poehler again and aired Sunday, January 12, 2014. Let’s take a look at the winners from the 201

  • Rebel SL1 RAW files unsupported by Aperture?

    I am having trouble importing CR2 files from my EOS100D/Rebel SL1. Aperture is reporting that the file type is unsupported. I'm guessing that it's due to it being a new file format? Does anyone have a solution for this as yet? many thanks in advance.