Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Strange Code in Preview

See original GitHub issue

Challenge standardize-times-with-the-html5-datetime-attribute has an issue. User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36. Please describe how to reproduce this issue, and include links to screenshots if possible.

I’m not really sure how to recreate this. The preview is displaying information that isn’t in the code-box. It appears to be doing this for several challenges. I’ve attached a snapshot from the lesson prior to this one. It’s still persisting on this challenge.

http://imgur.com/a/fcFRQ

<body>
<header>
  <h1>Tournaments</h1>
</header>
<article>
  <h2>Mortal Combat Tournament Survey Results</h2>
  
  <!-- Add your code below this line -->
  
  <p>Thank you to everyone for responding to Master Camper Cat's survey. The best day to host the vaunted Mortal Combat tournament is Thursday, September 15<sup>th</sup>. May the best ninja win!</p>
  
  <!-- Add your code above this line -->
  
  <section>
    <h3>Comments:</h3>
    <article>
      <p>Posted by: Sub-Zero on <time datetime="2016-08-13T20:01Z">August 13<sup>th</sup></time></p>
      <p>Johnny Cage better be there, I'll finish him!</p>
    </article>
    <article>
      <p>Posted by: Doge on <time datetime="2016-08-15T08:12Z">August 15<sup>th</sup></time></p>
      <p>Wow, much combat, so mortal.</p>
    </article>
    <article>
      <p>Posted by: The Grim Reaper on <time datetime="2016-08-16T00:00Z">August 16<sup>th</sup></time></p>
      <p>Looks like I'll be busy that day.</p>
    </article>
  </section>
</article>
<footer>&copy; 2016 Camper Cat</footer>
</body>

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

raisedadeadcommented, Jan 25, 2017

Yes, thanks @systimotic closing as a duplicate.

0reactions

systimoticcommented, Jan 25, 2017

I think there is a more fundamental issue with loopProtect running outside of Javascript code that should be fixed (see https://github.com/freeCodeCamp/freeCodeCamp/issues/12683, of which this issue is a duplicate, I think). @tmashuang Nice work on figuring out that the semicolon triggered loopProtect. We should probably dive into the source to see when it is activated.