Technical Documentation Page - User Story #13

User story : “When I click on a navbar element, the page should navigate to the corresponding section of the main-doc element (e.g. If I click on a nav-link element that contains the text “Hello world”, the page navigates to a section element that has that id and contains the corresponding header.”
my pen -
It performs exactly as described, yet still fails. I checked for typos and even spaces :frowning:

There was a space before the closing quotes in
href="#advanced_stuff" in your anchor tag and so the navigation for that link wasn’t working
When i cleared it, #13 is passed and the navigation also works

1 Like

I think error is because the last nav-link (advance_stuff) is in two lines… when i tried putting them in one line, the error is going.
And consider adding the script in top of your html page so that we can test from browser only…

1 Like

thank you.:star_struck:

I usually copied and pasted it in the fork-me link, but i’ll figure out adding the script! thanks :slight_smile:

if you need any help with that, i will be happy to help.

1 Like

No, figured it out already! appreciate it though

I will be glad if I am helped in checking what is wrong to this my practice test that user story 13 could not be passed in spite of all checks:

From the output of the assertion test

Check that these .main-section ids have corresponding href values : Functional_and_Non-Functional_Requirements,View_Front_End_Design_Architecture : expected 2 to equal 0

Check the href in each of your <a> tags

Check that all your target id are formed correctly. You have used - in one place and _ in the other

Thank you very much for the help, @alhazen1 . I am sincerely grateful.

1 Like

Hi guys,

Long time reader, first time poster.

Would any of you please be kind enough to troubleshoot why I cannot pass story .13 in the following fork:

Thank you in advance,