Nest an Anchor Element within a Paragraph Run test ISSUE

Tell us what’s happening:
So I have been stuck on the nesting anchors module for a week now. I have put in the code I believe to be correct. The problem is that when I go to Run Test nothing happens, I don’t get any feedback or task completion notification to move on to the next module. I have attempted to seek that module thinking it may be bugged. the same issue is on every one. I don’t know what to do at this point. I was using this as a method to practice prior to attending a code bootcamp in January. HELP!!!

Your code so far


<h2>CatPhotoApp</h2>
<main>
  <p> View more <a href="http://freecatphotoapp.com" target="blank"> cat photos </a>
  </p>
  
  <img src="https://bit.ly/fcc-relaxing-cat" alt="A cute orange cat lying on its back.">
  
  <p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>
  <p>Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.</p>
</main>

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134.

Link to the challenge:
https://learn.freecodecamp.org/responsive-web-design/basic-html-and-html5/nest-an-anchor-element-within-a-paragraph/

You added spaces inside the the anchor tag (around “cat photos”).

I removed the outside spaces around cat photos within the tag. still just shows running test… in the output box and nothing else for infinity it seems like. :face_with_raised_eyebrow:

It works when I run it. Are you by any chance using Edge, IE, or Safari as your browser? Free Code Camp has been updated to use newer technologies. It makes the application much faster and it means that we can go much longer without having to do a huge migration like the recent one. However, Edge, Internet Explorer, and Safari are very bad about choosing not to adhere to standards and support new functionality in JS and CSS. Right now, that means that these browsers exhibit lots of unexpected behavior. If you become a web developer you will come to hate these browsers with every fiber of your being.

lol, that may be the issue then. thanks for replying so soon to help. I’ll open (G)chrome. Yeah, quit my job and decided to move to Pittsburgh to pursue a career as a developer. I just enjoy learning this stuff.

problem resolved thanks again