Safari website rendering problems
I frequently experience black-and-white checkerboarding over part of a website image. Doing a hard reset tends to inhibit the problem for a short time. Clearing history & cache doesn't help. My phone's memory is about half-full, so space for cache isn't the issue. Zooming out on a website may restore the picture, but zooming back in brings the checkerboard back.
I'd appreciate ideas/solutions for stopping this.
And just to be clear... by checkerboarding, you mean you see checkerboards on the screen as placeholders for images, or parts of the images. Clear, black-and-white boxes in a checkerboard pattern.
Or do you mean the image isn't clear, as in it's pixellated... seen here: http://www.pcmag.com/encyclopedia_term/0,2542,t=pixelated&i=49324,00.asp
The first, I can't help you with, but the latter, has everything to do with the quality of the source image... and picture sites like the one you mentioned have their pictures and images set at the lowest possible quality so they transmit over the web quickly, and take up less bandwidth.
Similar Messages
-
Safari Keychain and Safari website identy problems
Recently, within the last 10 days, I've been getting a dropdown while in Safari that says " safari can't verify the identify website". This even occurs while accessing Apple. While not a big problem it is a nuisance. Does anyone know does apple have a fix in the works for this? Or is there a way to fix it. Also about 90% of the time when online I get a dropdown that states" Safari wants to use Keychain login". When I originally set up system Apple support advised me to delete keychain icon from main application screen, this I did, but keychain also exists under utilities icon. When I try to delete it here I get a message saying it can't be done because keychain is open. I can't find anyway to close it so I may delete it, any suggestions? Thanks
hey Delmer
welcome to the apple fourms
one thing that would come to mind here would be what verison of the OS are you running? 10.3 or 10.4 i would guess one of those so i would try these
your key chair in utilities you should not delete i find it strange that apple would just tell you to delete something like that what i would try doing is opening the keychan access in the utility folder where you can show your key chains there should be a certificate in the applications for safari which you can just delete off the list
if that doesnt work then click on keychain access in the main menu bar and run keychain first aid as well as a disk utility verifiy the disk and repair the permissions for this -
Safari Strange Rendering Problems-- Advice?
Hello-
Created a simple website - http://www.simdevgroup.com - and its rendering strangely in Safari. The text is jumbled and blurry. All other browsers are fine on both Mac and Windows.
Does it look ok to others or is it me? http://www.simdevgroup.com
Thanks!The text isn't jumbled or blurry here, on both iCab and Safari. But it looks better in Firefox, since the type is bigger (a big help with grey). But the light blue heads ("The Solution…") are smaller in Firefox.
-
Why does Safari have a problem loading images on some websites?
Safari has a problem loading pages properly or images on certain websites. Apple.com is one of the websites. On my way in here this time it didnt load any images on the front page. I emptied my cache and reloaded the page but that didnt help. Clicked on a broken image that took me to the proper page but without any images. Clicked on a different broken image on to the page and the images load no problem. Click back to the home page images load problem. Clicked on in to support forums and posted this topic.
Any ideas... it has done this for awhile. Everything is enabled in web content(preferences) Always accept cookies is selected.
ThanksHi all,
I occasionally see messages telling me that my software won't let me see the HTML version of an email, but it's there on the page when I open it. This happens mostly with emails from Apple, but have also had a similar message from a few of the photography mags that I subscribe to.
For my part, I just ignore it. It won't go away, but I just don't let it bother me. -
I just finished designing my website and it runs fine in
every browser but safari. it previews fine from dreamweaver in
safari but when i open it up on the server in safari it jsut
doesn't load everything or has problems with css. i'm not sure what
else to do. does anyone know or has had this problem.
www.outjogging.com is the website.PC or Mac? When I preview my sites with PC Safari 3.0.3 Beta
all the fonts are way too heavy, seems that its got rendering
problems, but since its a Beta I don't worry about these things
until its a full release.
Your website looks fine on Firefox 2.0.0.6 on my XP Pro SP2.
IE7 and IE6 look ok, apart from the linked image borders are now
blue.
Steve -
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> -
IE8, unusual rendering problem
I recently designed a new website (no dynamic content) using Dreamweaver CS4 for a small business client who has 5 networked PC's. All 5 PC's use IE as their internet browser -- 2 use IE6, 1 uses IE7 and 2 use IE8. On both computers using IE8, 1 page does not render properly -- the content is correct, but the CSS is off for an element that needs to float right, with text wrapping it. This element remains in normal document flow with no text wrap. The computers running IE6 and IE7 render everything correctly without problems.
Here's the strange part. I have a notebook computer and a desktop computer, both running IE8. Both my computers render all of the pages in the website perfectly. I'm going to try to view this website on a couple of other computers running IE8 to see if they render correctly or if they produce the same problem.
Based on my observations, I have to believe there's a problem with my client's 2 computers and the way their IE8 browsers are configured. Though I wasn’t there to observe, they assured me that they have cleared the cache and browsing history several times and manually "refreshed" the views. I'd expect that with a manual refresh the pages should render properly, but they are telling me they've done that and it has not corrected the problem.
Based on my testing, all of the pages render perfectly in IE8, and the latest versions of Firefox, Chrome, Safari and Opera. Furthermore, my client advised that their new website renders correctly on his smart phone (Google).
Is my thinking right on this, or am I missing something?Hi Nancy,
Wow! I've designed about a half dozen websites and have always thought I was
doing things correctly -- using Dreamweaver CS4 with "proper" CSS. I suspect
that most people use the default settings that come with their browser in terms
of text zoom / size and leave them there. For every website I've designed, once
I've checked my design using 5 different browsers in Dreamweaver CS4, it has
worked fine when I went "live," and none of my clients complained about the look
or the layout being strange.
This was a real eye-opener for me. I opened the "problem page" of my client's
new website in IE8 and it looked normal on my computer -- as I expected. Then,
per your suggestion, in the view drop down on the browser, I set the text size
to "small" and I instantly produced the incorrect layout that my client was
experiencing! It looks like if the user changes the text viewing size / zoom, it
can cause a serious problem in how the page actually looks. This does not appear
to be the case if you leave the text zoom / size alone and just set the zoom to
make the page larger or smaller.
I'll take a look at the link you provided for cross browser compatibility.
However, what I think I actually need is a way to either ensure that the browser
is at its default text size / zoom settings when the page is opened by the
browser, or else I need to find a way to deactivate the capability to change the
text zooming / size altogether. Are either of these actions even possible?
I use a standard box model, with no absolute positioning. I use element floating
and clearing as necessary, controlling my spacing through use of margins and
padding. I use some tables if needed, but I don't lay the whole .html page out
as a table like I've seen done commonly. Is a box model considered good
practice? I took many hours of on-line training in Dreamweaver CS4 website
design, and I don't remember any comments from the trainers about this issue of
text zoom / size and its effect on totally changing the look of the layout.
Clearly, it is an issue that I need to address.
Your help and comments are greatly appreciated!
Tom -
Safari not rendering Correctly
Hi-
Randomly, Safari stopped rendering sties correctly, actually, one site in particular. Gizmodo (www.gizmodo.com) only comes up as a sort of list instead of the correct full version. I've already reset Safari, clear cookies, history, temp files, etc. I also deleted the preference file, but to no avail. I'll attach a screenshot of this incorrect rendering to show you what I mean.
Thanks!!Hawaiian_Starman wrote:
Hi
I'm wondering if this is a Network problem. Site renders correctly for me using the latest WebKit build and Safari 3.0.4. Who is your Internet Provider? Are you using an Airport or Ethernet connection?
That would be weird because this only started happening about last week. I'll download the latest webkit and see if that helps any. My ISP is Verizon (FiOS). I am using the built in ethernet connection.
Here are my network settings:
Thanks for replying!
Message was edited by: Craig Cabrey -
I cleaned up my fonts today when Font Book flagged several fonts were duplicates or had other problems. I removed the fonts as suggested by FB and there were no immediate problems anywhere, not even Safari.
This morning, without having logged out or restarted Safari, it is rendering what appears to be Verdana with all characters as Cap A in a box.
I checked in Firefox if those pages rendered correctly, which they did, using Helvetica. So that indicates the standard CSS selection of fonts is being applied.
If I copy the wrongly rendered fonts from Safari and paste them into TextEdit they appear as normal text, no errors.
If I go into Appearance in Safari's preferences and choose +Standard font: Verdana+ it is substituted by odd ball Unicode boxed glyphs like TM or square root in the font field.
I tried switching to Lucida Grande or Lucida Sans but the font rendering problem remains. So it looks like the Verdana it is attempting to render is somehow misapplying Unicode characters.
Safari's Default Encoding is Western (ISO Latin 1). Switching to Unicode (UTF-8) is not fixing the problem either.
I can see no way of reinstating the fonts that were disabled.
This really has me scratching my head.
Any ideas?
Peter10th anniversary of OSX and Font handling is nearly as bad as the beginning.
Never had one problem fonts with a Mac.
"For an extensive look at font management and handling font problems in OS X, the following tutorial and FAQ by Kurt Lang is an excellent resource for anyone, but especially for those who extensively"use fonts: http://www.jklstudios.com/misc/osxfonts.html
Kurt Lang has been an Apple Discussions helper for years. He wrote the link that "baltwo" posted also.
Yes I'm aware of the contents of that link. Following some of those suggestions has got me in this situation.
I've yet to have anyone reply that the suggestions and advice given by Mr. Lang caused them any problems. You're the first. -
This one's a doozy. Website display problem iMac specific.
Alright, so I've been having this problem since day one and I've sucked it up for the past 2.5 years and I've been throroughly annoyed by now. So here's the problem.
Certain websites do not display properly. I do not believe that it is a browser problem because I've tried 3 different browsers (firefox, chrome, and safari) and the problem still persists. So let me post pictures first before I get in to the details:
Comparing the 3 different browsers.
(my concern is that the thumbnails do not display properly). The tabs are also not clickable (ie. I can't click "New Costco Coupons" from "Featured Deals").
So I have Parallels running, and opened up firefox to display the same websites that are giving me problems...
aeroplan thumbnails don't display. (left: windows; right: mac)
kickstarter website "Thanks a billion" doesn't display (left: windows; right: mac)
Kickstarter login page. (left: windows; right: mac): When I click login in windows, pop up opens for me to login. In mac, when I click login, nothing happens.
(the biggest issue that is getting under my skin)
And once again, redflags thumnails. (left: windows; right: mac)
I also believe this is an issue with this particular mac model. I have 2007 macbook pro with the same firefox plugins (they sync) and the same OS 10.9.2 (recently fresh installed on both machines, though the problem persisted before the OS install), and all these sites display fine.
This iMac model:
27-inch, Mid 2011
iMac 12,2
Model: A1312
2.7 GHz Intel i5
I've tried restarting in safe mode with plugins disabled and have ruled out a plugin problem. I've also checked and made sure that flash and java are all updated. Any help at all would be great =)Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of the test. -
Hi,
I have an .Net application running in LIVE. It was running Well in all Browsers(Chrome,Firefox,Safari), It also works good in Internet Explorer from version 6 to 10
Recently IE has Released 11th Version. when we open our APP in IE11 we have some major problems,
1) our application gets rendering problem
2) also the app is loading very slow.
All the above two issues are not completely happening in IE11,we have different Versions in IE11 (11.0.9600.17107, 11.0.9600.16521, 11.0.9600.16521IS, 11.0.9600.16659)
. out of these our app is completely working fine in "11.0.9600.16659". and the remaining
all other versions are getting different rendering errors.
We try to solve it by performing various additions to our app but no Use, we Placed MetaTag "<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE10">" and also we added APP_Browsers/ie.browser file which is downloaded
from NUGET Packages that which supports .net Framework 4. even though we are unable to find the issue what is going on here. even we also modified our code but no use. Can you Please Provide Help on This.Hi,
Here's a similiar thread in IE web development forum, that forum can better help you to find out a solution, we're not familiar with .net and issue about development.
http://social.msdn.microsoft.com/Forums/en-US/cefd324a-cce6-44ba-b1c0-e8dfc3209b30/rendering-problems-in-ie11?forum=iewebdevelopment
Thanks for your understanding.
Yolanda Zhu
TechNet Community Support -
Safari page load problems and 10.5.3
Since I have upgraded to 10.5.3, I am experiencing Safari page load problems on all my user accounts on my 2.0 GHz Core Duo Black MacBook. I have reviewed threads in this forum and that of the Safari forum with no solution that solves the problem. so I post here in hopes of additional expert solution ideas.
*The Problem:* Since upgrading to 10.5.3 Safari fails to complete page downloads for some, but not all websites. When these same websites are accessed with Firefox there is no problem. With Safari the page load will stop at about 75% completion, or the page will not load at all.
Here is an example of a webpage that will not complete: http://www.realclearpolitics.com/
Here is an example of a webpage that will not load at all: http://cherylsguitar.com/site (my wife's business)
I also have a G4 iMac running 10.4.11 on the same WiFi network that does NOT experience the Safari page load problems. All is good and speedy on this trusty machine.
*Solutions Attempted:*
- Deleted plist (with no effect)
- Re-installed Safari from Leopard disk (with no effect)
- Scoured User Preferences in Library for offending applications, plug-ins, etc.
- Reset PRAM
- Reset and examined cable modem and router (AirPort Extreme 802.11g)
*Hardware and Network info:*
- 2.0 GHz Core Duo Black MacBook
- 2 GB Ram
- AirPort Extreme Base Station (generation 1) running 802.11gAllan Eckert wrote:
Hi Perry Lehman;
Have you cleared out your cookies?
Allan
Allan,
Yes. I have reset Safari clearing all but website icons with no effect. I also tried turning of the Safari pop-up blocker with some very limited success. Disabling pop-up blocker will marginally help page load speed for some websites, but others still fail to load at all.
Thanks for taking time to post. -
Hi,
I'm having a problem with the newest updates to Safari. This problem did not occur until late december when I installed several updates via Software Update.
Problem:
I use a photo uploader on a website from my company (unfortunately I can't give out the URL, as it is protected). But it is similar to many other photo uploader sites - load a Java applet, drag images files into a Java window, the files are added to a upload list and then uploaded.
Now, if I drag 10 items into the window, only one or two will be added to the list. If I drag them in one at a time, all the images will be added. Previously it was possible to drag as many as one wanted in.
Now the really irritating part : During the upload, the Java uploader completely hijacks Safari. The window the uploader allways stays active on top. If I open a new tab or window the uploader window will reappear on top and dominate the action. The only way to get anything done while I am uploading photos is to open another browser like Firefox. Safari is completely occupied with the Java program.
Computer: MBP 2.16 GHz, 2GB RAM, OSX 10.4.11
Safari 3.0.4
Java 5.0 (not sure of the revision, but it is the most recent)
Any help would be greatly appreciated.I had similar Java problems with Safari and Firefox. I downloaded Navigator and now can run any Java app I need. One thing that may or may not have had any impact: when installing Nav, it asked if I wanted to import settings from Safari or Firefox. I chose not to import any settings. Works perfectly.
-
Rendering problem in output of Pages 5.1
Has anyone else seen a print rendering problem when trying to print a table in Pages 5.1?
All my text in tables is jagged and lower-resolution than other text:
(Printed from Pages 5.1 (1769) on a HP Color LaserJet CP2025 from a retina MacBook Pro original model running Mavericks 10.9.1.)
To see the problem, you must look at the full size image. Right-click to open it in a new tab.
The type is set to Helvetica 12 pt black.
The borders are set to 0.5 pt black. The top two lines have a border on all sides.
The top line's border is nearly invisible; on the full size image you should see a faint blueish line.
The middle line's box box is supposed to be
 a full box, but it is missing two sides. But at least this hairline renders properly.
The pdf of the same file looks fine on screen, even at high magnification. The problem only shows up in print.
The same problem exists in Numbers (where I first experienced it):
https://discussions.apple.com/message/24695801#24695801I see you followed Jerry's advice to post over here, and haven't got any responces, so I'll at least try to get a little more information into the discussion.
Since the document prints to pdf correctly, but not to the actual printer, it seems likely that it is a print driver issue. In the Numbers discussion on the issue, the original person with the issue was using a HP printer with a postscript driver. Since the HP support site was not very clear about whether a driver for that printer on Mavericks even existed, and the recommendation for a generic driver was for a PCL driver, not postscript, I suspect that they were not using a recommended configuration. It would probably be helpful to know the details about your printer and print driver.
Do you have access to more than one printer to test this on?
The new versions of Numbers and Pages are doing something strange in terms of how they copy tables to the system clipboard; the pdf version is no longer available, only bitmap images. Print to pdf, however seems to still get the pdf data. I don't think this should have anything to do with the data getting to the print driver, but it does seem consistent with your results. -
Follow up to recent posts regarding rendering problems
I've read all posts to Berrett below but can't seem to get my "Flip Video" camcorder (uses MPEG-4AVI) video into FCE without the rendering problem. I've tried to convert in two ways. Using MPEG Streamclip I transferred my video to my desktop using the "export to DV" command. It appears on desktop with a .DV suffix I then imported into browser. After editing in the viewer and trying to insert edit in canvas I get the message " "..clip does not match sequence settings..." I then click yes to change sequence settings and the clip moves to timeline. The video plays but the audio has to be rendered.
Next, I tried converting using the export to quicktime command in Streamclip with sound uncompressed and setting to DV-NTSC. When I insert into FCE and insert edit I get the sound but the picture has to be rendered. What am I doing wrong?
I've been working on this all day and am getting very depressed. Please help. Thanks.
Ed
SThanks but I think I tried that without success. I must have a setting somewhere wrong. My audio is fine but I still have to render my video. Using Streamclip to convert to quicktime here are the setting I used in the Movie Exporter dialog box.
Compression: Apple Motion JPEG A
Sound: uncompressed
frame size 720x480 (DV-NTSC)
In FCE my easy setup is
Format: NTSC
Use: DV-NTSC
Help.
Maybe you are looking for
-
How can I share my entire photo library from iCloud Drive?
I attempted to create a stream, but it only allows 5K photos and I have nearly 14K. Not being able to share iCloud Storage space seems to me to be counterintuitive to the concept family sharing.
-
I want to shuffle my streaming movies to play one after the other.
How to do this?
-
how do i fix this
-
Cant sync 3gs iphone with outlook 2007 calendar
Windows xp 3GS IPhone IOS 5.1.1 Itunes 10.6.1.7 Outlook 2007 USB connection
-
Doubts regarding CATS Record and CATS Release
Dear Experts. I am new to ESS_MSS area. My requirement is I need to add some UI fields to the CATS DATA RECORD screen. I have 15 components in the CATS business package. Please help me which is relevent component for this issue. Regards Shanmukha