Technical Documentation Page: sidebar size issue?

Technical Documentation Page: sidebar size issue?
0

#1

Hey guys,

I’m trying to pass the 5th project. Usually I’m finding my bugs after some time but this one is really testing me.

I’m trying to work out why the sidebar doesn’t pass the test.

Error message:
“1. On regular sized devices (laptops, desktops), the element with id=“navbar” should be shown on the left half of the screen. It should always be visible to the user and should remain stationary. You may need to enlarge the viewport or zoom out to ensure the navbar doesn’t scroll with the page content.”

But my sidebar is fixed in position, covers the left side of the screen and collapses with a media query, goes all the way to the bottom (even at 25% zoom). I’m struggling to find why FCC won’t give me a tick :smiley:

HTML:

<nav id="navbar">
  <header>
    <h1>JS Documentation</h1>
  </header>
  <a class="nav-link" href="#introduction">Introduction</a>
  <a class="nav-link" href="#what_you_should_already_know">What You Should Already Know</a>
  <a class="nav-link" href="#javascript_and_java">JavaScript And Java</a>
  <a class="nav-link" href="#HELLO_WORLD!">Hello World!</a>
  <a class="nav-link" href="#variables">Variables</a>
  <a class="nav-link" href="#declaring_variables">Declaring Variables</a>
</nav>

<main id="main-doc">
  <section id="introduction" class="main-section">
    <header>
      <h2>Introduction</h2>
    </header>
    <p>JavaScript is a cross-platform, object-oriented scripting language. It is a small and lightweight language. Inside a host environment (for example, a web browser), JavaScript can be connected to the objects of its environment to provide programmatic
      control over them.<br><br> JavaScript contains a standard library of objects, such as Array, Date, and Math, and a core set of language elements such as operators, control structures, and statements. Core JavaScript can be extended for a variety
      of purposes by supplementing it with additional objects; for example:
      <ul>
        <li>Client-side JavaScript extends the core language by supplying objects to control a browser and its Document Object Model (DOM). For example, client-side extensions allow an application to place elements on an HTML form and respond to user events
          such as mouse clicks, form input, and page navigation.</li><br>
        <li>Server-side JavaScript extends the core language by supplying objects relevant to running JavaScript on a server. For example, server-side extensions allow an application to communicate with a database, provide continuity of information from one
          invocation to another of the application, or perform file manipulations on a server.</li>
    </p>
  </section>

  <section id="what_you_should_already_know" class="main-section">
    <header>
      <h2>What You Should Already Know</h2>
    </header>
      <p>This guide assumes you have the following basic background:
      <ul>
        <li>A general understanding of the Internet and the World Wide Web (WWW).</li><br>
        <li>Good working knowledge of HyperText Markup Language (HTML).</li><br>
        <li>Some programming experience. If you are new to programming, try one of the tutorials linked on the main page about JavaScript.</li>
    </p>
  </section>

  <section id="javascript_and_java" class="main-section">
    <header>
      <h2>JavaScript And Java</h2>
    </header>
      <p>JavaScript and Java are similar in some ways but fundamentally different in some others. The JavaScript language resembles Java but does not have Java's static typing and strong type checking. JavaScript follows most Java expression syntax, naming
      conventions and basic control-flow constructs which was the reason why it was renamed from LiveScript to JavaScript.<br><br> In contrast to Java's compile-time system of classes built by declarations, JavaScript supports a runtime system based on
      a small number of data types representing numeric, Boolean, and string values. JavaScript has a prototype-based object model instead of the more common class-based object model. The prototype-based model provides dynamic inheritance; that is, what
      is inherited can vary for individual objects. JavaScript also supports functions without any special declarative requirements. Functions can be properties of objects, executing as loosely typed methods.<br><br> JavaScript is a very free-form language
      compared to Java. You do not have to declare all variables, classes, and methods. You do not have to be concerned with whether methods are public, private, or protected, and you do not have to implement interfaces. Variables, parameters, and function
      return types are not explicitly typed.</p><br>
  </section>

  <section id="HELLO_WORLD!" class="main-section">
    <header>
      <h2>Hello World!</h2>
    </header>
      <p>To get started with writing JavaScript, open the Scratchpad and write your first "Hello world" JavaScript code:</p>
    <div class="graybox">
      <pre><code>function greetMe(yourName) {
  alert("Hello " + yourName);
}
greetMe("World");</code></pre>
    </div>
    <p>Select the code in the pad and hit Ctrl+R to watch it unfold in your browser!</p><br>
  </section>
  
  <section id="variables" class="main-section">
    <header>
      <h2>Variables</h2>
    </header>
      <p>You use variables as symbolic names for values in your application. The names of variables, called identifiers, conform to certain rules.<br><br>
      A JavaScript identifier must start with a letter, underscore (_), or dollar sign ($); subsequent characters can also be digits (0-9). Because JavaScript is case sensitive, letters include the characters "A" through "Z" (uppercase) and the characters "a" through "z" (lowercase).<br><br>
      You can use ISO 8859-1 or Unicode letters such as å and ü in identifiers. You can also use the Unicode escape sequences as characters in identifiers. Some examples of legal names are Number_hits, temp99, and _name.</p><br>
  </section>
  
  <section id="declaring_variables" class="main-section">
    <header>
      <h2>Declaring Variables</h2>
    </header>
      <p>You can declare a variable in three ways:<br><br>
      With the keyword var. For example,</p>
    <div class="graybox">
      <code>var x = 42.</code>
    </div>
    <p>This syntax can be used to declare both local and global variables.<br><br>
      By simply assigning it a value. For example,</p>
    <div class="graybox">
      <code>x = 42.</code>
    </div>
    <p>This always declares a global variable. It generates a strict JavaScript warning. You shouldn't use this variant.<br><br>
      With the keyword let. For example,</p>
    <div class="graybox">
      <code>let y = 13.</code>
    </div>
    <p>This syntax can be used to declare a block scope local variable.</p>
    <div class="graybox">
      <code>Sidebar issue doesn't exist: this fits the bill, surely?</code>
    </div>
  </section>
</main>

CSS

* {
  margin: 0;
  padding: 0;
  box-sizing: border-box;
  font-family: "Raleway", sans-serif;
  color: #222;
}

body {
  width: 100vw;
  background: #cee8f5;
}

#navbar {
  position: fixed;
  top: 0;
  left: 0;
  bottom: 0;
  right: 0;
  background: #8dc2dc;
  border-right: 2px solid gray;
  width: 280px;
}

#navbar header {
  text-align: center;
  padding: 32px 0;
}

.nav-link {
  display: block;
  text-decoration: none;
  padding: 12px 16px;
  border-top: 1px solid black;
}

#main-doc {
  margin: 30px 30px 30px 310px;
}

.main-section p {
  padding: 15px 20px;
  font-size: 14px;
}

.main-section ul {
  margin-left: 40px;
  font-size: 14px;
  list-style-position: inside;
  padding-right: 20px;
}

.graybox {
  width: auto;
  background: #f5dbce;
  margin: 15px 40px;
  padding: 15px;
  overflow: scroll;
}

code {
  font-family: monospace;
  color: #434343;
}

@media (max-width: 600px) {
  #navbar {
    position: relative;
    height: 250px;
    width: 100%;
    overflow: scroll;
    border-bottom: 2px solid gray;
  }
  .nav-link {
    text-align: center;
    padding: 6px;
  }
  #main-doc {
    margin: auto;
    padding: 20px;
  }
}

Your browser information:

User Agent is: Mozilla/5.0 (X11; CrOS x86_64 10718.88.2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.118 Safari/537.36.

Link to the challenge:
https://learn.freecodecamp.org/responsive-web-design/responsive-web-design-projects/build-a-technical-documentation-page

Thanks to anyone who can point me in the right direction! :slight_smile:


#2

And a link to my Pen:


#3

All seems to be OK here!


#4

That’s bizarre… I’m still getting only 15/16 :face_with_raised_eyebrow:


#5

But it’s good to know that I’ve got a reason to be going a bit nuts looking for the error haha


#6

Make sure you run your tests on a big screen. For some reason, the tests passes for me only when the code pen viewport width is 866px or larger.


#7

Ahh that’s great. I have a tiny 11" chromebook so that explains why I’m not passing. Thanks so much for your help :slight_smile: