IE Nav Trouble

HTML & CSS
21

so, instead of targeting only bad ie (ie6-7), going the boilerplate/js frameworks path got you in more trouble in shorter time.

i guess it’s time for:

But maybe I can tell the HTML5 Boilerplate creators that their efforts are backfiring.

or maybe waste time to better learn those only to find out you’ve wasted time on ephemeridae. this doesn’t seem like a productivity boost to me :slight_smile: see now why nobody really wanted to waste time with your mixed up page?

22

Getting things worked out with separate IE-only style sheets (I know that adds a style sheet to the mix but I don’t see a way around it).

23

actually, it turns out the boilerplate/js frameworks path had nothing to do with the problem or the solution so your comment is meaningless; thanks though; if you don’t know what some of the code does then this might be a learning opportunity for you

if i had time i could explain to you how the code is not mixed up; some of the code is necessary to deal with IE, and different versions of IE; you could take it out but then find that you have to put it back in

having said that i’m still improving the code and cleaning it up all the time;

24

maybe i understood wrong :slight_smile:

but i do expect some explanations from you, if you find the time, on how

some of the code is necessary to deal with IE, and different versions of IE; you could take it out but then find that you have to put it back in

and especially how html5 boilerplate will help you with js turned off :wink: modernizr rocks… on the bottom of the sea!

oh, and you seem to use an outdated version anyway. you should be changing your page to that:

  • Removed -webkit-font-smoothing: antialiased; it makes monospace too thin.
  • IE conditional classes have moved from the <body> tag to the <html> tag.
  • Dropped text-rendering: optimizeLegibility as it breaks small-caps and looks odd on Linux machines.
  • Added a IE6 call for the minified dd_belatedpng.
  • Revised viewport declaration to allow user scaling and clear Webkit console errors.
  • Updated Modernizr to 1.6.

oh, and have you looked at your page w/o css, js, images? it says nothing to the visitor.

oh, and the flickers on the menu?

what am i to learn? how to make a useless garbage web site? no, thank you. you’re doing just fine :slight_smile:

25

Well, some of the stuff is necessary for the overall functioning of the site. The example page (which I cobbled together rather quickly) does have some code in it that doesn’t apply to it. I hold my code to a high standard and don’t mind others holding me to a high standard. Thank you everyone (Stevie D, svcghost, and noonnope) for the responses.

As far as different versions of IE go you can handle some of the issues with JavaScript, but with js turned off you can fall back on IE conditional comments and utilize those the best you can. Every project may require a different mixture. If you use js to add transparency to images in IE but then the user turns js off then they just don’t get the transparency. But it still helps to have that JavaScript in.

26

good luck. let us know how it went.

27

Thanks. I’ll probably be able to post the link to the real site next week. It’ll be pretty good but I did so much cool stuff on this site that then got yanked out of my control and totally ruined. Another day in the life of a web developer…

28

i have no doubt it’ll be cool :cool:

will it be accessible?

will we see any sign of progressive enhancement or graceful degradation we can’t see right now?

will it be efficient? will it be maintainable?

these above make the “IE Nav Trouble” a little exceeded :slight_smile:

29

Yes to all the above to the degree that budget and time constraints allow. My skills can cover all of that. I am currently fine tuning the styles to display the pages properly on handheld devices. When I started this job I basically sat around for the first six weeks waiting for the graphics to come in that should’ve been ready the day I started. But my own deadline for completion didn’t change. One example I coded in of progressive enhancement just got overruled by the powers that be so that I had to roll it back to the less cool version; some progressive enhancement will definitely still be in place though.

30

noonnope, when I said “cool” I largely meant “progressive enhancement and graceful degradation.” Anyways, the site is now up at: http://corporate.local.com I was the development lead on it but in numerous ways I had code of mine subsequently changed by others (humans and machines; one bad example is the CMS forcing extra code in at the top of the document) and/or taken out of control before I felt like I had properly completed it. Still, it could’ve been a lot worse.

31

hi MauiMan2.

there are some things that need fixing. there are 66 Errors, 30 warning(s) when you validate the page.

more importantly, you have weird placements, weird elements, weird duplicates:

<HTML> 
 <HEAD> 
[...]
</HEAD>
<BODY><html lang="en" class="no-js"> 
 
    <head> 
[...]
	</head> 
 
[...] 
        
        <header> 
[...]
        </header> 
[...]
            <footer> 
[...]
            </footer> 
[...]
 </BODY> 
</HTML>

on a html transitional DTD.

user experience suffers. when first hovering menus the images disappear, flicker, are showing slow.

i say it can very easily be better.

32

You completely missed the part where I said the CMS put extra stuff into the header and that I had not control over it. The whole following part is included by the CMS:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<!---------- Begin document V05.10,P=Corporate.local.com,A=Home : Local.com,D=Home : Local.com,V=25------>

<HTML> 
 <HEAD> 
<TITLE> 
Home : Local.com
</TITLE>
</HEAD> 

<BODY>

I had thought about then using that as the header but then I wouldn’t be able to have the doctype I want or the stuff in the HEAD element that I need there.

You may have also missed other things I said about how code was wrested from my control and then ruined. Thanks though. :mad:

33

I’m not sure I see the point in using a system that breaks pages and ruins usability. Aren’t they supposed to make things easier for developers? I hate broken crappy CMSes. : (

34

Yes, it was beyond frustrating that a CMS that would do that was used. Now prospective employers are going to see it and think I don’t know what I’m doing, just like others in this thread think. I should learn from them that people will give me zero benefit of the doubt.

35

MauiMan: can you switch to some less-soul-killing CMS? The kind that doesn’t make you bald from pulling your own hair out?

36

I didn’t have any say in the matter. But I think after my all my grouching about it they are saying they might switch. But the emphasis is on “might” and if they do switch it’ll likely be after I’m gone.