Hi Everyone I've been trying to fix the css for my product pages, If it looks right on fire fox, then it doesn't on IE and vice verson. For example http://www.weddingandgems.co.uk/crystal-tiara-021-p-116.html looks right in the Fire Fox but not IE. Here's the css file for the product listings can any one spot what I'm missing. #mainProductBox { margin: 0 auto; padding: 0; } #imagebox { margin:0; padding-top:0px; width: 200px; float:right; border: 0px; border-style: solid; border-color: #948c96; } #productMainImage { margin:0em 0em 0em 0em; } #productbox { margin:0; padding:0; width:270px; float:left; } h1#productName { margin:0; padding:0; font-weight:700; text-align:center; line-height: 2em; color: #976994; } #productDescription { margin:0; padding:0px 0px 0px 0px; font-size: 10pt; } #productPrices { margin:0; padding: 2px 0; font-weight:700; text-align:left; font-size:12pt; } #productDetailsList { margin: 0; padding:0; list-style: none; } #productDetailsList ul { margin: 0; padding:0; list-style: none; } #productDetailsList ul li { padding:3px 0 3px 3px; } #freeShippingIcon { width:50%; height:54px; } #productPurchaseBox { margin: 0 auto; } #buybox { margin:0; padding:3px; width:45%; text-align:center; float:left; } .wrapperAttribsOptions { margin:1em 0; text-align:left; } #attribsOptionsText { margin:0; padding:0.5em 5px; text-align:center; } .optionName { margin:0; color:#580c84; font-weight:700; padding-left:3px; text-align:left; width:11em; } #cartAdd { margin:1em; padding:3px; font-size:1em; text-align:center; } #cartImage { margin:0.5em 1em; } #QuantityDiscountsBox { margin: 0; width: 30%; float: left; } Code (markup): Any suggestions will be appreciated. THanks Kerrie
Well... If you have more than one stylesheet on the home page without different media types, you are probably doing something wrong. If you are using javascript to get around the target attribute being deprecated in your doctype, you are probably doing something wrong. If every one of your links is an absolute, you are probably doing something wrong. If you have a 25k HTML file for less than 3k of actual page content, you are doing something wrong. If you have tables that only have ONE TD inside them, you are DEFINATELY doing something wrong. 86 Validation errors, menu's not marked up as lists, presentational markup, presentational images loaded in the markup, no text fallbacks for images as text, meaningless redundant alt text, insufficient contrast on visual elements making the white text areas effectively illegible, illegibly small fixed metric fonts, unneccessary classes, use of entity spaces for indenting, unneeded line breaks inside block level containers... My advice, chuck it in the trash and drop the grand on having someone who understands HTML and CSS rework it - as what you have is an unsalvagable train wreck. As I'm fond of saying, there's more of 1998 to this than 2008.
deathshadow - what do you think is the best way to achieve the target="_blank" effect in strict 1.0? I always thought javascript is the only option for this.
The answer is simple. So simple it's starting you in the face: DON'T - It was deprecated FOR A REASON!... That reason being you aren't supposed to do what target does unless you have frames. Abusing it for _blank is an accessability /FAIL/, an annoyance for a number of users, and in general is a matter of overriding the default behavior of a link. Personally, having a normal link open in a new window with no CHOICE given to me as to whether it does or not PISSES ME OFF - I want it to open in a new tab I'll middle click on it - otherwise leave the behavior the hell alone. There are only a handful of situations where target="_blank" or the javascript equivalent are appropriate like opening up a help box or preview on a form... You have none of that.
Thank you for mentioning the exception, ds. OP: The Javascript option is simply a way to cheat-- to keep your HTML "valid" and strict while forcing new windows on your clients, which as deathshadow said, was invented so people could go from frame to frame on a frame-built page. I personally think it's more honest when, in the rare situation as above where new windows save unsubmitted form data from being accidentally lost, to drop down to a transitional doctype, use target=blank, and TELL in both the help text AND the title text that it opens in a new window to warn your visitors. Do the users still get to choose? Yes, if they have a browser that tabs, they can still either set their settings to override your target attributes and open in a new tab instead, or right-click and select Open In A New Tab. Nobody has to bitch aout control for the users then-- they always can override target and have been able to for some many years now. I'll even wager there's an override possibility for those using JAWS and WindowEyes-- I'd be surprised if there wasn't. But target-imitating Javascript is pretty far down the list of things to fix-- save it for last.