Inactive Navigation Bar

Discussion in 'HTML & Website Design' started by aaronsiegel, May 3, 2014.

  1. #1
    Over the last 3 months I've been building websites with Adobe Dreamweaver. Through stackexchange and Youtube, I've been able to solve most of my problems and this has been quite rewarding however, in the course of building my most recent site, I've run into a bit of a stumbling block. Actually, it's more like a wall.

    I have a sidebar which, despite the html and css, REFUSES to operate in my browser. It fails to illuminate the mouse curser and the links don't work.

    In the link below you will see the sidebar I'm describing.
    http://canadaeikaiwa.jp/Index.html

    Strangely enough, when the sidebar (the html and css) are copied and then placed in a blank page, it works!

    I simply can not understand why the sidebar won't work in the context of the rest of my webpage.

    Anyone who can help me solve this problem will put a frustrating and time devouring search which began nearly a month ago!

    Thanks
    Aaron
     
    aaronsiegel, May 3, 2014 IP
  2. Hoyt Hamilton

    Hoyt Hamilton Peon

    Messages:
    3
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #2
    I went into the source, and found the sidebar. I tried to access each page through its URL and they are not there. These webpages are not located in the same folder your index.html file is.
     
    Hoyt Hamilton, May 4, 2014 IP
  3. aaronsiegel

    aaronsiegel Peon

    Messages:
    4
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #3
    Hoyt,
    Thanks for looking into my issue here.

    If the links on the navigation bar work without these webpages, why do I need them in the folder for my sidebar?
    Aaron
     
    aaronsiegel, May 4, 2014 IP
  4. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #4
    I'm sorry you've been led down the garden path like that. Only thing you can learn from Dreamweaver is how not to build a website; you have likely picked up teriffyingly bad habits that are biting you in the backside code-wide... Though since your page seems to also be chock full of turdpress "I can haz intarnets" endless pointless classes for nothing you likely got a nice big double-whammy out of it.

    Now, that said It LOOKS like this might be a depth sorting issue -- one of your other elements on the page may be overlapping it... using element inspection I can't find which one that might be however...

    But really... with the markup proudly declaring itself in the first line to be in transition from 1997 to 1998 coding practices, static CSS in the document, jquery-tardery pissing on the page's speed and usefulness, NAME attributes on elements that shouldn't even HAVE names, presentational images in the markup, endless pointless classes and ID's for nothing, fixed width layout, illegible color contrasts, incomplete forms, paragraphs around non-paragraph elements, no alt text on content images (and instead that stupid malfing HTML 5 "DATA-" and "ROLE" attributes that don't even EXIST in your chosen doctype)... well, it's hardly a surprise to see 20k of bloated nonsense for 452 bytes of plaintext and a half dozen content images (easily 2 to four times how large your html should be) and 18 validation errors. (that if you were using a RECOMMENDATION doctype of HTML 4 Strict or XHTML 1.0 Strict would magically turn into around four dozen errors).

    It's a laundry list of how not to build a website, which is why my advice would be to pitch the steaming pile of overpriced halfwit manure known as Dreamweaver in the trash, grab yourself a flat text editor (Flo's notepad2, notepad++, editPlus, gEdit, Sublime, pick one, they're ALL free), and start over from scratch taking the time to learn semantic markup, separation of presentation from content, accessibility minimums as suggested by things like the WCAG... and since this is a turdpress mess, you may have to learn how to bend that idiotic buggy steaming pile over the table to make it your ***** so it's not trying to shove bloated halfwit endless pointless classes down your gullet -- or learn how to build a page without the current crop of garbage CMS; It's sad, but nobody working on these CMS systems seem to know enough HTML or CSS to be telling anyone else how to do a blasted thing!

    There is little if anything I'd even try to salvage from that mess. It's just another laundry list of how not to build a website.

    -- edit -- hah, it's the jquery-tard menu up top that's causing the problem. It's not hiding the dropdown frames properly so it's overlapping everything after it. Just part of why I say anyone who tells you to use JavaScript on a menu doesn't know enough on the topic to be giving anyone advice.
     
    deathshadow, May 4, 2014 IP
  5. Hoyt Hamilton

    Hoyt Hamilton Peon

    Messages:
    3
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #5
    The thing is the links don't work, though. I get a 404 when I click on them up top. I mean they are clickable, but none of the links on your webpage work at all. Most of the images won't even load.
     
    Hoyt Hamilton, May 4, 2014 IP
  6. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #6
    That's NOT what's being asked, he knows the locations are BS and 404, that's NOT the issue when working on a template -- the ones in #sideBar can't be clicked on AT ALL. As in you put the mouse over them, there's no 'hand', and you can't click on them... well, unless you're some sort of idiot using IE, as they seem to work in IE8/lower -- but not in FF, Opera or Chrome.

    Which is why it's a depth-sorting / painters-algorythm issue -- likely caused by the scripttardery and buggy/broken markup.
     
    deathshadow, May 4, 2014 IP
  7. aaronsiegel

    aaronsiegel Peon

    Messages:
    4
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #7
    Hey Deathshadow,

    your right, the links aren't important at this point. I just posted the page on another hosted website's server so you guys would be able to see the problem with the side bar.

    What do you mean when you say that " hah, it's the jquery-tard menu up top that's causing the problem"? Neither deleting the script nor deleting the jquery menu solves the issue with the side bar.

    Thank you both for spending time on this problem.
    A
     
    aaronsiegel, May 4, 2014 IP
  8. kk5st

    kk5st Prominent Member

    Messages:
    3,497
    Likes Received:
    376
    Best Answers:
    29
    Trophy Points:
    335
    #8
    See this:
    
    #white-page {
      -moz-border-bottom-colors: none;
      -moz-border-left-colors: none;
      -moz-border-right-colors: none;
      -moz-border-top-colors: none;
      background-color: #FFFFFF;
      border-color: #524D4F;
      border-image: none;
      border-style: solid;
      border-width: 0 0 0 2px;
      box-shadow: 0 0 5px rgba(0, 0, 0, 0.7);
      color: #FFFFFF;
      font: 13px/20px Helvetica Neue,Helvetica,Arial,Sans-serif;
      height: 100%;
      margin-bottom: 22px;
      margin-left: auto;
      margin-right: auto;
      overflow: hidden;
      padding: 0;
      position: relative;
      width: 960px;
      z-index: 0;
    }
    Code (markup):
    I don't know if any browser properly handles negative indexes. Zero z-index puts the element on the canvas and you can't get any lower anyway.

    Frankly, for a fairly simple layout, there's a whole lot of crap that appears to have been flung at the wall hoping for stickage. Hope is not a plan, it's what gives you tired-head.

    cheers,

    gary
     
    kk5st, May 4, 2014 IP
  9. aaronsiegel

    aaronsiegel Peon

    Messages:
    4
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #9
    HAH! Gary!

    I just changed the z index to zero and my side bar started working!! I'm so unbelievably happy right now.
     
    aaronsiegel, May 4, 2014 IP