See if that works...

Post #49,440 by Yendor 8/15/02 3:41:18 AM Reply	See if that works... Spent a couple hours online with someone with an IE browser tonight. Here's what we did. Removed the base "a" style definition, and turned replicated the code that was in there for each section. So now there's "#Content>a" "#Menu>a" etc. But that still didn't really fix IE. Looked fine in Mozilla, so I left those in there. But IE was still broken. So I added "class" definitions to all my <a> tags in the HTML itself, and then copied (again) all of my "a" CSS definitions. "a.menu", "a.content:link", "a.footer:visited", etc. Those are in addition to "#Menu>a", "#Content>a:link", "#Footer>a:visited", etc. So basically, I've doubled my CSS code for links. In addition, all of the HTML <a> tags now have class definitions (<a class=menu>) as well as being inside a "div" tag of the same name. Somebody, please tell me that there's a simpler way to do this than having to double your code inside all your files? IE is really fucked up, and it's really starting to annoy the shit out of me... -YendorMike What if the hokey pokey really is what it's all about? - Jimmy Buffett, June 20, 2002, Tinley Park
Post #49,548 by static 8/16/02 12:34:04 AM Reply	Hard to say what's wrong. I've noticed myself duplicating CSS for no apparant reason other than that seems to be what it takes. But some thoughts for you to consider: You're not confusing ID selectors (e.g. #Menu and ID='Menu') with class selectors (e.g. .Menu and class='Menu') are you? Also, #Menu>A:link is more restrictive than #Menu A:link as the latter means you can put something else between the #Menu'ed tag and the A tag. Wade. "Ah. One of the difficult questions."
Post #49,551 by Yendor 8/16/02 2:04:25 AM Reply	Re: Hard to say what's wrong. But some thoughts for you to consider: You're not confusing ID selectors (e.g. #Menu and ID='Menu') with class selectors (e.g. .Menu and class='Menu') are you? Also, #Menu>A:link is more restrictive than #Menu A:link as the latter means you can put something else between the #Menu'ed tag and the A tag. No, I'm not confusing ID selectors with class selectors. I first tried it with only ID selectors like <div id="Menu"> in my HTML, and #Menu>a:link in my CSS. In that particular instance, my pretty menu box that showed up with white links on an orange background in Mozilla was a completely orange box in IE. What I did to fix it was add class="menu" attributes to all of the <a> tags in the HTML, and duplicate the "a" definitions in the CSS to be a.menu as well as #Menu>a. I can't say as I truly understand why that works, but it does. IE is borked. -YendorMike What if the hokey pokey really is what it's all about? - Jimmy Buffett, June 20, 2002, Tinley Park
Post #49,552 by static 8/16/02 2:15:53 AM Reply	Try this. Make the div <div class='Menu'>. Make your CSS selector .Menu instead of #Menu. Change the #Menu>A:... selectors to .Menu A:... and remove the class= from the <A> tags. You should also be able to then remove the a.menu selectors. In my reading, the W3C standard is a little unclear about how style elements cascade from ID selectors whereas class selectors are better defined in that regard. Then too, I haven't played much with ID selectors. :-) Wade. "Ah. One of the difficult questions."
Post #49,623 by Yendor 8/16/02 5:45:55 PM Reply	WOO! That worked! Double-coding removed, and it reportedly still works in IE. Life is good, and Wade roX0rz. Thankee sai. -YendorMike What if the hokey pokey really is what it's all about? - Jimmy Buffett, June 20, 2002, Tinley Park
Post #49,667 by static 8/17/02 4:21:11 AM Reply	bows Nice to see my long hours of trying to fathom the W3C's CSS document is useful to someone else. :-) I know it's a bit belated, but you might like to browse [link\|http://yceran.org\|my web site] for other CSS ideas. Wade. "Ah. One of the difficult questions."
Post #49,689 by Yendor 8/17/02 12:28:17 PM Reply	Re: bows Looks good, Wade! Browses quite nicely in Mozilla 1.0. You also reminded me to download Opera, if only to test that my site works in it. (It does.) Kudos! -YendorMike What if the hokey pokey really is what it's all about? - Jimmy Buffett, June 20, 2002, Tinley Park
Post #49,568 by JayMehaffey 8/16/02 10:47:07 AM Reply	What I've been doing I've been working on converting an internal application from MSAcess to a web app. I've taken the chance to update my web knowledge and update our internal standards. I'm still studing the CSS specs and examples, so there may be problems that I havn't encountered or understood yet. But what I have been doing that has worked well so far is to use class based selectors for everything. My motivation for doing so was entirly based on the problems of sharing ID based sheets between multiple pages and programmers though, not anything to do with inheritance problems. To me, ID based selectors seems to be for putting little page specific tweeks on top of your general style sheet. Jay

Welcome to IWETHEY!