Stuck on replacing article with div tag - Wrap Content in the article Element

Hi Everyone,

I am stuck on the “Applied Accessibility: Wrap Content in the article Element” lesson.

It’s a simple lesson where you are supposed to change the div tag to use an article tag instead.
But I keep getting this message: “Your code should not have any div tags.” , even though I have replaced the div tags with article tags.
Seems to be a bug, or am I missing something? Did anyone else experience this?

EDIT: Seems to be an issue with Firefox, the code gets accepted by the editor in Chrome.

This is the code without any div tags that is getting rejected:


<h1>Deep Thoughts with Master Camper Cat</h1>
<main>
  <article>
    <h2>The Garfield Files: Lasagna as Training Fuel?</h2>
    <p>The internet is littered with varying opinions on nutritional paradigms, from catnip paleo to hairball cleanses. But let's turn our attention to an often overlooked fitness fuel, and examine the protein-carb-NOM trifecta that is lasagna...</p>
  </article>  

  <img src="samuraiSwords.jpeg" alt="">

  <article>
    <h2>Defeating your Foe: the Red Dot is Ours!</h2>
    <p>Felines the world over have been waging war on the most persistent of foes. This red nemesis combines both cunning stealth and lightening speed. But chin up, fellow fighters, our time for victory may soon be near...</p>
  </article>

  <img src="samuraiSwords.jpeg" alt="">

  <article>
    <h2>Is Chuck Norris a Cat Person?</h2>
    <p>Chuck Norris is widely regarded as the premier martial artist on the planet, and it's a complete coincidence anyone who disagrees with this fact mysteriously disappears soon after. But the real question is, is he a cat person?...</p>
  </article>
</main>

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0.

Link to the challenge:
https://learn.freecodecamp.org/responsive-web-design/applied-accessibility/wrap-content-in-the-article-element

I’ve just copy n paste your code and works fine, maybe it’s just a bug. Try to reload the page.

Hm, seems to be an issue with Firefox, just tried it on Chrome and it gets accepted there.