Curious bug with Adjust Margin challenge Beta

Challenge adjust-the-margin-of-an-element has an issue. User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36. Please describe how to reproduce this issue, and include links to screenshots if possible.

Challenge requires camper to change margin: 10px; to margin: 20px; for .green-box { background-color: green; padding: 20px; margin: 10px; }

When running it initially the test processes it fine and accepts the answer. However, if I close the pop-up message instead of continuing to the next challenge and then Clear my Code using the Reset button (in order to play with the code before moving on, for example), the bug occurs. When repeating the challenge (changing 10px to 20px for green box, all other code left alone) and submitting Run Test, the code will automatically revert to 10px every time.

I’ve gotten it to stop the behaviour both by refreshing the page or by typing and then backspacing a space elsewhere, then Running Test again. The bug also does not appear if I type or alter code elsewhere in the editor.

It is repeatable in Incognito mode for Chrome, but when trying to repeat the issue for Firefox I could not get it to accept the solution of 20px whatsoever.

<style>
  .injected-text {
    margin-bottom: -25px;
    text-align: center;
  }

  .box {
    border-style: solid;
    border-color: black;
    border-width: 5px;
    text-align: center;
  }

  .yellow-box {
    background-color: yellow;
    padding: 10px;
  }
  
  .red-box {
    background-color: red;
    padding: 20px;
    margin: 20px;
  }

  .green-box {
    background-color: green;
    padding: 20px;
    margin: 20px;
  }
</style>
<h5 class="injected-text">margin</h5>

<div class="box yellow-box">
  <h5 class="box red-box">padding</h5>
  <h5 class="box green-box">padding</h5>
</div>

[nicksavov]

I tested on a Windows computer with Firefox 57 and I couldn’t reproduce the issue.

@Skarrix @systimotic @Douglasdc3 , could you check the issue one more time? Looks like it’s resolved.

[systimotic]

Thanks for checking this @mpontus @nicksavov! Some recent changes to the beta fixed this issue.

Happy coding!