RE: [WSG] IE6 problem - more general
Hi Susie, I am not an expert by any means. I joined this group to learn from others and get some tips. I try to tackle other people's problems because it s a great way to learn and hopefully I can help someone out in the process. I have read a number of books on CSS (and other web related topics) and found the best explanation of the CSS model for me was in CSS Mastery Advanced Web Standards Solutions by Andy Budd. A couple of techniques I use when debugging: 1) put a border around the problem area and surrounding or enclosing blocks using border: solid red 1px; 2) remove HTML and/or CSS chunks to try to isolate the problem. Sometimes by removing some HTML the problem goes away then that tells me where the issue lies. Hope that helps. Regards, Kepler _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susie Gardner-Brown Sent: Monday, May 14, 2007 7:07 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] IE6 problem - more general Hi there Kepler Thank you! I believe it's OK now. I would really like to ask you how you know all this - how you keep it in your head?!! Do you have pages and pages of stuff like this written down, or what?!!! For example: about making nav buttons clickable in IE7: why does the container div need to be 'position: relative for IE7? And what if there wasn't a container div? Would that make it not work at all?! I really need to get a handle on how to keep all these things 'known' to me! I've got a quite good book - The CSS Anthology, by Rachel Andrews. But it's pre-IE7 ... Any thoughts, suggestions would be great! Thanks again ... :) - susie On 15/5/07 6:37 AM, Kepler Gelotte [EMAIL PROTECTED] wrote: Hi Susan, To make the navigation buttons clickable in IE7 you need to define the container as position: relative: #container { position: relative; } Also the pseudo links should be defined for :link and :visited if you define It for :hover. Try using these for the navigation definitions: #leftNav a:link, #leftNav a:visited { /* instead of #leftNav a */ #level2nav a:link, #level2nav a:visited {/* instead of #level2nav li a */ Regards, Kepler *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] IE6 problem - more general
There is also an abundance of information left from those who initially discovered and tried to squash the IE family rendering bugs. Any google search for IE6 box model bugs or anything of the like will return a complete education's worth of material. In the long run its all experiencing each bug and understanding what caused it and knowing that ahead of time, next time you begin marking up a layout. When I first started doing layouts with CSS, I thought IE had it right and the other browsers were wrong! Slowly I learned through trial and error, and for a time even did hybrid layouts using minimal tables as I got a stronger grasp of the issues I was facing. The most important things you can do as you create layouts are to: * Make sure you're using strict document types and validate your code before anything else * Test everything in browsers that work first * Set up separate stylesheets for IE so you don't have to use hacks Those points make life much easier in the battle against IE's rendering issues. *Joseph R. B. Taylor* Sites by Joe, LLC /Custom Web Design Development/ Phone: (609) 335-3076 www.sitesbyjoe.com http://www.sitesbyjoe.com Kepler Gelotte wrote: Hi Susie, I am not an expert by any means. I joined this group to learn from others and get some tips. I try to tackle other people’s problems because it s a great way to learn and hopefully I can help someone out in the process. I have read a number of books on CSS (and other web related topics) and found the best explanation of the CSS model for me was in “CSS Mastery Advanced Web Standards Solutions” by Andy Budd. A couple of techniques I use when debugging: 1) put a border around the problem area and surrounding or enclosing blocks using “border: solid red 1px;” 2) remove HTML and/or CSS chunks to try to isolate the problem. Sometimes by removing some HTML the problem goes away then that tells me where the issue lies. Hope that helps. Regards, Kepler *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Susie Gardner-Brown *Sent:* Monday, May 14, 2007 7:07 PM *To:* wsg@webstandardsgroup.org *Subject:* Re: [WSG] IE6 problem - more general Hi there Kepler Thank you! I believe it’s OK now. I would really like to ask you how you know all this – how you keep it in your head?!! Do you have pages and pages of stuff like this written down, or what?!!! For example: about making nav buttons clickable in IE7: why does the container div need to be ‘position: relative” for IE7? And what if there wasn’t a container div? Would that make it not work at all?! I really need to get a handle on how to keep all these things ‘known’ to me! I’ve got a quite good book – The CSS Anthology, by Rachel Andrews. But it’s pre-IE7 ... Any thoughts, suggestions would be great! Thanks again ... :) - susie On 15/5/07 6:37 AM, Kepler Gelotte [EMAIL PROTECTED] wrote: Hi Susan, To make the navigation buttons clickable in IE7 you need to define the container as position: relative: #container { position: relative; } Also the pseudo links should be defined for :link and :visited if you define It for :hover. Try using these for the navigation definitions: #leftNav a:link, #leftNav a:visited { /* instead of #leftNav a */ #level2nav a:link, #level2nav a:visited { /* instead of #level2nav li a */ Regards, Kepler *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.467 / Virus Database: 269.7.1/805 - Release Date: 5/15/2007 10:47 AM *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] IE6 problem - more general
On Tue, 15 May 2007 10:36:17 -0400, Kepler Gelotte wrote: 1) put a border around the problem area and surrounding or enclosing blocks using border: solid red 1px; But be aware that a border can alter the layout. (By trapping margins that normally escape for example.) My preference is to add colored backgrounds to the main blocks. Viz: #content {background: #ccf;} #header {background: #fcf;} #sidebar {background: #ffc;} I put these at the end of the main style sheet where I can delete them easily when done. Of course, this is just for IE, which I test last. When developing the layout I find Firebug invaluable. It is the only tool I know that shows you where the margins are. (Negative margins excepted.) Cordially, David -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] IE6 problem - more general
On Tue, 15 May 2007 10:36:17 -0400, Kepler Gelotte wrote: 1) put a border around the problem area and surrounding or enclosing blocks using border: solid red 1px; But be aware that a border can alter the layout. (By trapping margins that normally escape for example.) My preference is to add colored backgrounds to the main blocks. Viz: #content {background: #ccf;} #header {background: #fcf;} #sidebar {background: #ffc;} I put these at the end of the main style sheet where I can delete them easily when done. Of course, this is just for IE, which I test last. When developing the layout I find Firebug invaluable. It is the only tool I know that shows you where the margins are. (Negative margins excepted.) Cordially, David -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] IE6 problem - more general
Hi there Kepler Thank you! I believe it¹s OK now. I would really like to ask you how you know all this how you keep it in your head?!! Do you have pages and pages of stuff like this written down, or what?!!! For example: about making nav buttons clickable in IE7: why does the container div need to be position: relative² for IE7? And what if there wasn¹t a container div? Would that make it not work at all?! I really need to get a handle on how to keep all these things known¹ to me! I¹ve got a quite good book The CSS Anthology, by Rachel Andrews. But it¹s pre-IE7 ... Any thoughts, suggestions would be great! Thanks again ... :) - susie On 15/5/07 6:37 AM, Kepler Gelotte [EMAIL PROTECTED] wrote: Hi Susan, To make the navigation buttons clickable in IE7 you need to define the container as position: relative: #container { position: relative; } Also the pseudo links should be defined for :link and :visited if you define It for :hover. Try using these for the navigation definitions: #leftNav a:link, #leftNav a:visited { /* instead of #leftNav a */ #level2nav a:link, #level2nav a:visited {/* instead of #level2nav li a */ Regards, Kepler *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] IE6 problem - more general
Hi, I am like you merely trying to keep a grasp of the situation I have glanced over this article today http://www.smashingmagazine.com/2007/05/10/70-expert-ideas-for-better-css-coding/ featuring some ideas from Rachel Andrews. and I hate to be the bearer of bad news but its still not clickable in IE6 - S On 15/05/07, Susie Gardner-Brown [EMAIL PROTECTED] wrote: Hi there Kepler Thank you! I believe it's OK now. I would really like to ask you how you know all this – how you keep it in your head?!! Do you have pages and pages of stuff like this written down, or what?!!! For example: about making nav buttons clickable in IE7: why does the container div need to be 'position: relative for IE7? And what if there wasn't a container div? Would that make it not work at all?! I really need to get a handle on how to keep all these things 'known' to me! I've got a quite good book – The CSS Anthology, by Rachel Andrews. But it's pre-IE7 ... Any thoughts, suggestions would be great! Thanks again ... :) - susie On 15/5/07 6:37 AM, Kepler Gelotte [EMAIL PROTECTED] wrote: Hi Susan, To make the navigation buttons clickable in IE7 you need to define the container as position: relative: #container { position: relative; } Also the pseudo links should be defined for :link and :visited if you define It for :hover. Try using these for the navigation definitions: #leftNav a:link, #leftNav a:visited { /* instead of #leftNav a */ #level2nav a:link, #level2nav a:visited {/* instead of #level2nav li a */ Regards, Kepler *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] IE6 problem - more general
Sigh ... !!! Well, apart from that - Thanks for the link. That looks really useful! Cheers susie On 15/5/07 9:32 AM, Sam Sherlock [EMAIL PROTECTED] wrote: Hi, I am like you merely trying to keep a grasp of the situation I have glanced over this article today http://www.smashingmagazine.com/2007/05/10/70-expert-ideas-for-better-css-codi ng/ http://www.smashingmagazine.com/2007/05/10/70-expert-ideas-for-better-css-cod ing/ featuring some ideas from Rachel Andrews. and I hate to be the bearer of bad news but its still not clickable in IE6 - S On 15/05/07, Susie Gardner-Brown [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi there Kepler Thank you! I believe it's OK now. I would really like to ask you how you know all this how you keep it in your head?!! Do you have pages and pages of stuff like this written down, or what?!!! For example: about making nav buttons clickable in IE7: why does the container div need to be 'position: relative for IE7? And what if there wasn't a container div? Would that make it not work at all?! I really need to get a handle on how to keep all these things 'known' to me! I've got a quite good book The CSS Anthology, by Rachel Andrews. But it's pre-IE7 ... Any thoughts, suggestions would be great! Thanks again ... :) - susie On 15/5/07 6:37 AM, Kepler Gelotte [EMAIL PROTECTED] wrote: Hi Susan, To make the navigation buttons clickable in IE7 you need to define the container as position: relative: #container { position: relative; } Also the pseudo links should be defined for :link and :visited if you define It for :hover. Try using these for the navigation definitions: #leftNav a:link, #leftNav a:visited { /* instead of #leftNav a */ #level2nav a:link, #level2nav a:visited {/* instead of #level2nav li a */ Regards, Kepler *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***