Bug in apex_4_0.css

Hi everybody,
It's not a big issue but nevertheless an error:
the style "apex_size_bar" defined in apex_4_0.css has a bad attribute:
url(none)
This is not correct. You will see some HTTP-404 on your Application Server
because /i/css/apex_4_0.css is reuqesting /i/css/none, for example when you edit a region (where /i/ is youre image prefix)
NB: you will recieve NO error on your client, all works fine!
Fix: delete the attribute
url(none)
in
apex_4_0.css.
Kind regards,
w
Edited by: wko on Jan 10, 2011 1:10 AM
Edited by: wko on Jan 10, 2011 1:11 AM

Thanks for letting us know!
We will have a look to fix that in the next release.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Similar Messages

Looks like a bug in RoboHelpX6 - CSS

I have been working in RoboHelpX6 on some CSS - Initially I
updated an existing CSS, and changed the font that was being used.
Was using Tahoma and changed it to Verdana, when I did this the CSS
lost the word wrap. I then went and created a new CSS from scratch,
stated it out with Tahoma like the first one, everything worked
fine. Went in and changed the font to Verdana and again lost the
word wrapping!!!
Any reports on this yet?

RoboHelp x5 rewrote CSS as well. I'm pretty sure they think
it's a feature.
The workaround I developed involves authoring/editing the
.css files outside RH, keeping them under version control, and
reverting them whenever RH tries to change them, plus copying clean
.css files over the rewritten ones after projects have been
generated.
Note that for every stylesheet fname.css you have, RH will
create a supposed "Netscape" version of the stylesheet called
fname_ns.css. Again, I'm pretty sure they think this is a feature.
Unless you like the way the _ns.css version looks on
Netscape/Firefox/whatever, you will want to copy your clean
fname.css over fname_ns.css as well.
Amy

Bug in pagination CSS on these support forums

Hi
Just noticed the pagination buttons in these forums are screwed to the right side... and then i searched and found that in this file, you have a css entry .cf { } which is empty... i assume it should have { clear: both } ?
This is the css file which has it empty
http://support.cdn.mozilla.net/media/css/common-min.css?build=2e2daad
And here's a screenshot of how it looks now
http://scr.hu/screenshooter/0640523/ypubyvb
Thanks

I use this code in userContent.css to fix this issue and style that section (I like to dim stuff).
<br />
<pre><nowiki>@-moz-document domain(support.mozilla.org) {
ol.pagination {margin:5px 0!important;padding:0!important;float:right;clear:both;opacity:0.5}
ol.pagination:hover {opacity:1}
ol.pagination a {font-weight:bold;font-size:1.3em!important}
}</nowiki></pre>

Minor bug in core_V22.css

Warning: Unknown property 'margion-bottom'. Declaration dropped.
Source File: /i/css/core_V22.css
Line: 128
null

Thank you for reporting this. I have fixed this for Application Express 4.1.
Joel

Flex 3 CSS won't compile, HELP!!!

As you can see in this image, design view finds the assets
just fine, but it has compile errors. ->
Flex CSS
Foolishness
Any suggestions???

Flex's css stuff seems to freak out occasionally. I find
doing a clean build or a restart of the app helps. If not, then you
probably have some bug in your CSS that isn't obvious that throws
things off. Try removing each section of CSS until you see which
section is causing the problem, then narrow it down.
Also, keep in mind that assets are relative to their files
and that can be problematic at times, especially when going from
dev to production.
I generally have my folders look like:
src
views
assets
bin-debug
lib
etc...
I have my style.css in the assets folder along with my embeds
and I still include everything as ../assets/ because they are
relative to the src/App.mxml that they were included in as opposed
to the location of the CSS file I believe.

Small jquery-ui i18n bug

Sorry about posting this here, don't know where else to put it.
this file: /i/libraries/jquery-ui/1.8/ui/i18n/oracle/jquery.ui.datepicker-nb-no.js is missing translation of some labels.
this file: /i/libraries/jquery-ui/1.8/ui/i18n/oracle/jquery.ui.datepicker-no.js is correct, both files should be identical.
easily fixed " cp jquery.ui.datepicker-no.js jquery.ui.datepicker-nb-no.js "

<head>
<title>JQuery Tab</title>
<link rel="stylesheet" href="/i/themes/theme_20/theme_3_1.css" type="text/css" />

<link rel="stylesheet" href="/i/css/apex_4_0.css" type="text/css" />
<link rel="stylesheet" href="/i/libraries/jquery-ui/1.8/themes/base/jquery-ui-1.8.custom.min.css" type="text/css" />
<script type="text/javascript">var apex_img_dir = "/i/", htmldb_Img_Dir = apex_img_dir;</script>
//jquey loaded here
<script src="/i/libraries/jquery/1.4.2/jquery-1.4.2.min.js" type="text/javascript"></script>
<script src="/i/javascript/apex_4_0.js" type="text/javascript"></script>
<script src="/i/javascript/apex_legacy_4_0.js" type="text/javascript"></script>
<script src="/i/javascript/apex_widget_4_0.js" type="text/javascript"></script>
<script src="/i/javascript/apex_dynamic_actions_4_0.js" type="text/javascript"></script>
<script src="/i/libraries/jquery-ui/1.8/ui/minified/jquery-ui-1.8.custom.min.js" type="text/javascript"></script>
//jquery ui and css loaded here
<link rel="stylesheet" href="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.2/themes/redmond/jquery-ui.css" type="text/css" />
<script src="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.2/jquery-ui.js"> </script>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>VIEW Source of IE 7 show the above.. which clearly show that jquery is already loaded ... any clue...
Regards,
Shijesh

CSS IE Fix please

Hi,
I am aware there are bug fixes for CSS issues in IE. Please
can you take a look at my test page which is fine in FireFox but
falls appart in IE.
TEST PAGE
HERE
For info I am exploring accessibility and these should expand
nicely when you press ctr (cmd mac) + to increase text size.
Thanks,
Rich

On Mon, 31 Mar 2008 15:37:40 +0000 (UTC), "RICH POW"
<[email protected]> wrote:
>Hi,
> I am aware there are bug fixes for CSS issues in IE.
Please can you take a
>look at my test page which is fine in FireFox but falls
appart in IE.
>
>
http://www.adelantedesign.co.uk/http://www.adelantedesign.co.uk/button.html
>
> For info I am exploring accessibility and these should
expand nicely when you
>press ctr (cmd mac) + to increase text size.
>
> Thanks,
> Rich
He just pasted link twice
http://www.adelantedesign.co.uk/http://www.adelantedesign.co.uk/button.html
>
http://www.adelantedesign.co.uk/
http://www.adelantedesign.co.uk/button.html
the reason it won't expand nicely with Ctrl + is because you
are using
Absolute links ( layers )
and it's inside a frame ?
~Malcolm~*...
~*

Screen draw bugs?

Has anybody experienced these bugs in Dreamweaver CSS for the
Macintosh:
a.) When you have multiple windows open at once and you "step
back" from them in Expose to view them all at once, some or all of
them display as blank white sheets.
b.) When you drag a window to reposition it on your screen,
it displays in both locations until you click on it in its new
location.
c.) Sometimes when you mousedown + drag your cursor over a
bit of text to highlight it, the highlighting fails to show on the
screen, although the text you have chosen is in fact selected and
can be cut, copied, etc.
d.) Suddenly and inexplicably a page of text will start
displaying in a different font than the one you chose, and you have
to quit and reopen the document to get the font back.
I'm curious to know if I am unique in experiencing these
problems, or whether they are common. I suspect the latter, since I
am using a Mac Pro that is pretty much out-of-box, with the
original graphics card and so forth. Or is there some other
software I could have on my computer that could possibly interfere
with DW working properly.

Has anybody experienced these bugs in Dreamweaver CSS for the
Macintosh:
a.) When you have multiple windows open at once and you "step
back" from them in Expose to view them all at once, some or all of
them display as blank white sheets.
b.) When you drag a window to reposition it on your screen,
it displays in both locations until you click on it in its new
location.
c.) Sometimes when you mousedown + drag your cursor over a
bit of text to highlight it, the highlighting fails to show on the
screen, although the text you have chosen is in fact selected and
can be cut, copied, etc.
d.) Suddenly and inexplicably a page of text will start
displaying in a different font than the one you chose, and you have
to quit and reopen the document to get the font back.
I'm curious to know if I am unique in experiencing these
problems, or whether they are common. I suspect the latter, since I
am using a Mac Pro that is pretty much out-of-box, with the
original graphics card and so forth. Or is there some other
software I could have on my computer that could possibly interfere
with DW working properly.

WebDAV not working over SSL on CSS11503

SOME HISTORY
As you may recall we had an issue with interoperability between our WebCT Vista application and the Cisco CSS11503 Load Balancer. In a nutshell the Load Balancer would inject custom HTTP headers into HTTP packets, but only into the first HTTP packet of a TCP session. With your help we've learned that Cisco will change this in the August release of the CSS software.
OUR NEW PROBLEM
We are now having a related problem. In short, we cannot get WebDav to work over SSL. That is, when connect from Client to Load Balancer via SSL, and then Load Balancer to Web Server via plaintext, our application fails. Conversely, when we maintain a clear text connection straight through from Client to Web sever WebDav works.
After doing some network traces of WebDav connections both with and without SSL I think we've discovered the cause of the problem: the Load Balancer fails to add our custom HTTP header "WL-Proxy-SSL: true" to HTTP "PROPFIND" requests, even though it correctly adds them to the HTTP "OPTIONS" requests.
HOW WE CONFIGURED THE LOAD BALANCER
We configured our Load Balancer with the Global configuration of
http-method parse RFC2518-methods
and with the command
ssl-server 20 http-header static "WL-Proxy-SSL: true"
so that the header "WL-Proxy-SSL: true" will be passed with the HTTP headers used for WebDav was well as with the 'standard' HTTP headers "GET, POST, HEAD", etc.
Below is the relevant passage from the "CSS Command Reference" at
http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_750/cmdrefgd/cmdgloba.htm#wp1432749
======================================================================
"By default, a Layer 5 content rule supports the HTTP CONNECT, GET, HEAD, POST, and PUT methods. Unless configured, the CSS recognizes and forwards the following HTTP methods directly to the destination server in a transparent caching environment, but does not load balance them:
OPTIONS, TRACE, PROPFIND, PROPPATCH, MKCOL, MOVE, LOCK, UNLOCK, COPY, and DELETE.
When you enable the CSS to support all RFC-2518 methods, the CSS parses the Request-URI field in an attempt to match a Layer 5 rule. If the contents of the Request-URI field are not in a compliant format of an absolute URI or an absolute path, the CSS tries to match the field to the next best wildcard ("/*") rule. If the match fails, the CSS attempts to match the Layer 4 rule, and then the Layer 3 rule."
========================================================================
I interpret this to mean that when we configure "http-method parse RFC2518-methods" that the load balancer will treat all the HTTP headers in the group "OPTIONS, TRACE, PROPFIND, ...", etc the same as the "standard" HTTP headers "GET, POST, HEAD", etc.
As I said earlier our network traces show that the "WL-Proxy-SSL: true"
header present in the HTTP header OPTIONS but *not* in the header "PROPFIND".
A BUG IN THE CSS COMMAND PROCESSOR?
By my reckoning, this behaviour must be a bug in the CSS Command processor, because whatever the CSS does for the "OPTIONS" header it should also do for the "PROFIND" header.
ATTACHMENTS
I've included three attachments.
trace.txt
- text output from Ethereal of the network trace
on the web server, with comments.
webdav.ssl.snoop
- the original network trace in Sun's 'snoop' format.
css.2.cfg
- the running configuration on the CSS11503
Thanks in advance for your help.

Hi
I finally discovered what is the issue here. In appears that in case of unsigned applets, the code is unable to access SunJCE provider which contains most of the ciphers used by SSL protocol. This means that a session with SSL server is broken and effectively applet is not initialised.
This problem is related to configuration of JRE under linux due to export control restrictions. Unfortunately I don't know how to make JRE to use SunJCE by default.
As a workaround I have set up the following policies using Policy Manager:
grant {
permission java.security.SecurityPermission "putProviderProperty.SunJCE";
grant {
permission java.lang.RuntimePermission "getProtectionDomain";
grant {
permission java.lang.RuntimePermission "accessClassInPackage.sun.security.*";
I don't know how insecure my actions are, but this definitely fixed problems with applets under SSL / HTTPS.
Feel free to send me your ideas how to fix this issue in more elegant way.
Best,
Marcin

Cannot adjust page width to fit to screen size on some PCs with IE

Hello friends, I am using APEX 4.0 and IE9 on different Windows 7 PCs . The page will go way off the screen to the right on one PC, and fits nicely inside the screen on another PC. This problem does not occur in Firefox on any PC. I have used Firebug to try to isolate the template or css settings. Using Theme_4, I have a breadcrumb region and 4 reports regions. One of the reports regions is in column 1 and 3 regions are in column 2. Display point is Page Template Body (3. Items above region content) for all the reports regions. The CSS is #themes/theme_4/css/theme_4_0.css. The template is One Level Tabs (Right Sidebar/Table Based). I tried various width="" using px and % under Edit Page Template-Definition-Body (see below). I tried style="width:800px" within the <div> tags. I have tried various other changes to theme_4_0.css and apex_4_0.css with no visible change to the page width on the obstinate PCs. I reset IE setting and deleted all personal settings on both PCs with no changes to either one, one fits on the screen and the other does not. The issue is that most of our users use IE so most of them will have to live with using the horizontal scroll bar to see the regions in column 2, unless we switch them all to Firefox (not a bad option, except that option works for our users only, we have no control over external browsers). I have tried suggestions from many discussion threads, as this problem has bothered us for quite some time. I know this is an IE problem, but any help is appreciated. Thank you.
"|" represents screen size and "-" is the regions/content for the "bad" PCs.
|----------|----------
The "good" PCs look like this:
|----------|
Peter
<div id="body">
<table class="tbl-body" cellspacing="0" cellpadding="0" border="0" summary="">
<tbody>
<tr>
<td class="tbl-main" width="100%">#REGION_POSITION_02##BOX_BODY#</td>
<td class="tbl-sidebar">#REGION_POSITION_03#</td>
</tr>
</tbody>
</table>
</div>

BD...
I think your concerns are very reasonable. But I want to sort of refocus things a little bit for you here... it's not really a PC vs Mac issue... Rather, it's specifically an Internet Explorer issue. And you might say that this is synonymous...still 98% of the world uses IE, and you would be correct. Hopefully when the final version of IE7 comes out, it will finally embrace some of the modern day OPEN web standards without trying to make too many standards of its own (this is Microsoft, though).
Anyways, in the meantime, I guess we all try to make the best of it. It's very easy to conclude that iWeb is not a viable tool for you, as long as you have something else to "fall back" on. With my limited knowledge of all things HTML, I have no such luxury. Instead, I have put up a notice on my site for IE users only that the site might not look its best on IE....this notice also encourages IE users to use FireFox, which is very much like Safari and will in 99% of cases display your iWeb pages just like you expect. You can see how I've done this here (but you have to surf from IE)... http://blog.dirtdoog.com
I think many people in the PC world understand the limitations of IE. Certainly many don't, but you have to consider your likely audience, I guess. I believe that your website content is king. If your content is compelling enough to your intended audience, they will jump through hoops to see it in its full glory....but you have to make them aware of the problem. That's why I have chosen to take the path that I have taken.
Let me know what you think.

Spry Navigation 2.0 - Spacing for div for nav bar

Hello:
I am once again working on an navigation bar that renders somewhat differently in various browsers (problems with IE 8 & 6). The navigation is to fit into a div that is bordered by a gold coloured border top and bottom (top border is attached to the header). The problem is one of calculating the appropriate height based on the settings for the custom nav css file. I have taken the font size, padding (top and bottom) and border (top and bottom) together with padding on the overall container of the nav bar. Accordingly I have set the height of the navigation container div at 41px. In most browsers this works fine, however there are some glitches that cause excess white space to appear either above the navigation bar or below it, thus separating the border from the navigation bar.
The url for the site is http://socls.org/PCLC-testing/CorePages.html
I have included the css for the custom nav settings, and the css relating to the navigation in the general css file as well as a screen shot of IE 8.
Thanks for any help in advance.
Steve.
The custom nav css is as follows:
@charset "UTF-8";
/* CSS Document */
/* 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 right pointing 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, all submenus 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 level menu 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 on the 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:#7888c7;
    font-family: Arial, Helvetica, sans-serif; /* Specify fonts on on MenuBar 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;
    border-color: #4457a2 #333366 #2c3868 #4457a2;
    border-width:3px;
    border-style: none none none none;
/* 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: 0px 24px 0px 0px;
    background-color:#7888c7;
    border-width:3px;
    border-color: #8899cf #566a99 #333366 #8899cf;
    border-style: solid solid solid solid;
#MenuBar .MenuItemFirst {
    border-style: solid solid solid solid;
#MenuBar .MenuItemLast {
    border-style: solid solid solid solid;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:center;
    line-height:1.4em;
    color:#331e0d;
    background-color:#7888c7;
    padding: 6px 15px 6px 39px;
    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: normal;
    font-size: 14px;
    font-style: normal;
    background-color:#7888c7;
    padding:0px 2px 0px 0px;
    border-width:3px;
    border-color: #8899cf #333366 #333366 #8899cf;
    /* Border styles are overriden by first and last items */
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:center;
    line-height:1em;
    background-color:#7888c7;
    color:#331e0d;
    padding: 6px 12px 6px 5px;
    white-space:normal;
    width: 210px;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: #3b4b8d;
    border-color: #5266b7 #14192f #14192f #5266b7;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: #3b4b8d; /* consider exposing this prop separately*/
    color: #fefefe;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: #3b4b8d;
    color: #fefefe;
#MenuBar .SubMenu .MenuItemHover {
    background-color: #3b4b8d;
    border-color: #5266b7 #14192f #14192f #5266b7;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: #3b4b8d;
    color: #fefefe;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: #7888c7;
    min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
    border-color: #3b4b8d #3b4b8d #3b4b8d #3b4b8d;
    border-width:0px;
    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 the MenuItemContainer. 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: #7888c7;
    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 for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. 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 lot of these needed, the plugin does not generate the extra classes for modern 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.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: #3b4b8d; /* consider exposing this prop separately*/
    color: #fefefe;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: #3b4b8d; /* consider exposing this prop separately*/
    color: #fefefe;
.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 */
The css for the page in general (as it relates to the navigation bar) is:
#main_nav_contents {
    width: 960px;
    height: 41px;
    position: relative;
    padding-left:0px;
    border-bottom: 3px solid #C56F2C;

Hello Again:
Based on some recalculations I realized that with a font size of 17px, 6px padding (top and bottom = 12px) and 3 px border (top and bottom =6) that the height of the nav container should be 35px; I have change the general style sheet to reflect that change, but still have rendering problems accross browsers.
To perhaps add clarity, the following is a screen shot of how it appears in most browsers, and how I intended it should look.
Thanks (again) in advance for any help that can be offered. Steve.

Bottom right corner resize controls trump vertical scroll button if set to appear in the bottom corner

My bottom right corner square of the Firefox window normally sits below the bottom of the vertical scroll bar and right of the horizontal scroll bar if one exists. The square is used to click and drag to resize the window's right and bottom boundaries.
At issue is when a web site places its vertical scroll down-arrow button in the bottom right corner. I cannot access the down-arrow button with my mouse to cause the page to scroll down a few lines at a time because when I point the mouse there, I get the resize controls instead. Even though the down-arrow button is plainly visible on the screen, the resize controls take charge and I cannot use the scroll control.
Two example web sites display their down-arrow control at the very bottom of the window; TIME.com and GMAIL.com. I have also viewed two PDF documents in the browser, and they too, have a vertical scroll bar all the way to the bottom, and I cannot use that down-arrow button because instead I get the northwest-southeast click-to-resize cursor instead of the mouse pointer when I attempt to use that button for scrolling.
Someone on the Google Help forum was not able to replicate that issue, showing me screenshots of his lower right corner mouse behavior. He does not have the resize control covering access to the scroll bar.
I am using the latest Firefox, I have reset Firefox, thus dumping all of my add-ons and custom settings, and have only put back AdBlock Plus and Cookie Monster. And Troubleshooter, when I asked a similar question.
I am running Windows XP, on its last days of support. This computer is not capable of running anything newer, unless I run with Linux.
Going to TIME.com, its vertical scroll is in the bottom corner and I get the resize control arrows instead of the mouse pointer when I point to the down-button. If I disable page styles in the View menu, I get a useful output that sets the end of the vertical scroll above the bottom corner. So somebody's idea of styling the page (CSS) creates this issue for me.
Going to Gmail, turning off the styles gives me a useless output of nonsense, so I must use page styling enabled.
Can someone please give me some guidance? This forum page has vertical and horizontal scroll above and left of the bottom corner square. I have access to all the parts of both scroll bars, as is the case on most well-designed pages.
My window-resize controls are in charge always of the bottom corner square even if the vertical scroll is supposed to be there.
See also my first wording of this question: https://support.mozilla.org/en-US/questions/993519

Those layout.css prefs are about enabling some CSS feature, in this case vertical writing, so have nothing to do with scroll bars.
*Bug 772321 - implement CSS parsing of writing-mode property
*resource://gre/greprefs.js
<pre><nowiki>// Is support for CSS vertical text enabled?
pref("layout.css.vertical-text.enabled", false); </nowiki></pre>
Can you attach a screenshot?
*http://en.wikipedia.org/wiki/Screenshot
*https://support.mozilla.org/kb/how-do-i-create-screenshot-my-problem
Use a compressed image type like PNG or JPG to save the screenshot.

Has anyone had issues with Planning security refreshing in Essbase

I am on Planning version 9.3.0.1 and we are having issues with planning users being able to use an essbase connection to pull data from smartview. They are able to see data in web forms in planning but they get #no access when they try to connect to the same data in smartview.
Has anyone else experieced this issue.

If user works when you provision individually its because they were set in the environment in EAS.
group has to have all the access needed (bug in orig). css file open a ticket for the file name. example user needs calc access you setup calc but bug in system is not also giving user read and write access. Thus you can individually add this to the group in provisioning area in shared services. in EAS goto File open- editors create/run script with
alter user 'userID' Add application_access_type Planning;
alter user 'userID' add application_access_type Essbase; to add user to the environment if error you need to refresh eas first then run maxl script for planning you also need to go to workspace and select any of your dimensions all your groups ...edit .. migrate identities.. to get group/Users in planning wether adding or removing users. when you do planning changes you need to do database and security filters refresh.

Thumbnails and preview wrong size

Has anyone got any ideas on why some of the books we have had made for us in the past now have incorrect thumbnail/preview page dimensions (see screenshots)?
Is it an iBooks bug or a CSS, XHTML problem?
Thanks,
Anthony

Tony
The network drive is a 4TB Raid 5 WDSharespace supporting Mac files - all other family laptops and desktops are Apple.
However in checking yesterday I did find that the network drive is degraded and that 1 of the internal disks appear to have failed - today I will get a replacement and have it rebuild, and will also get a firewire linked drive to connect direct to my computer to house my photo library (WDSharespace will be backup) and will check how Aperture is working after going through this. I do not see how the drive could affect what aperture is doing to the thumbs and Previews but worth being absolutely sure the setup is 100% before returning to the issue.
Tks

Exporting books in epub format

Hi!
is there anyone, who is producing design heavy ebooks in epub format ott of Indesign cs55?
OMG. IMHO the whole export filter is one bog software bug!
The output code is mess. In CSS it mixes different measurement units, it losts object tags, and creates a whole lot of is own generated tags when exporting long docuqments organized as InDesign books.
Do you know, is there any alternative to Adobes own epub export? Or how to use CS50 epub export in CS55?
Ants Tuur

Yes. Maybe i expressed myself wrong. For producing coffe table books, the DPS is the best.
What i am doing is producing textbooks and other books full of images and tables.
I am totally baffled with the amount of bugs Adobe new epub export script includes. I mean -- I got the book with a lot of content and therefore split to several ID files compiled to the book. Whwn i expirt that book, the same tag from different files got his own name: body-1, body-2, body-3, etc. How to overcome it?
And there i a lot od this kind of bugs.
The CSS in epub is the mess.
Im i realy the olny one, who got those problems?
A.

Bug in apex_4_0.css

Similar Messages

Maybe you are looking for