Change:
], "tests": [ "assert.strictEqual(convert('Dolce & Gabbana'), 'Dolce &amp; Gabbana', 'should escape characters');", <ins> "assert.strictEqual(convert('Hamburgers < Pizza < Tacos'), 'Hamburgers &lt; Pizza &lt; Tacos', 'should escape characters');", "assert.strictEqual(convert('Sixty > twelve'), 'Sixty &gt; twelve', 'should escape characters');", "assert.strictEqual(convert('Stuff in "quotation marks"'), 'Stuff in &quot;quotation marks&quot;', 'should escape characters');", "assert.strictEqual(convert("Shindler's List"), 'Shindler&apos;s List', 'should escape characters');", </ins> "assert.strictEqual(convert('abc'), 'abc', 'should handle strings with nothing to escape');" ], "MDNlinks": [

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The sample calculator for does not allow integer 0 to be the first operand. To reproduce, go to the calculator link, try pressing 0, followed by an operation. Or just start using operations starting from the default screen, which shows a 0. You will see the operation appear on its own without a first operand. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: 67.0.4 (64 bit) Operating System: MacOS Mojave If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! This is the result of hitting the 0 pad followed by the X pad followed by the 9 pad 3 times. You can continue entering other operations, and numbers, but the = pad will not do anything at this point. Must hit AC and start over.
is there any update on this? if not i whould like to try to fix this since robert didn't update this :)
Hi thanks for drawing my attention to this. can you please check the linked PR and confirm the action item on this?
/cc
Hi sorry for the late response and thank you both for your patience and for reporting this. I tested the changes in and it seems to solve this issue. I'll merge that once the tests pass and update the code on CodePen.

Challenge has an issue. This bonfire needs more tests. It's too easy to get them passed. Now it checks only &. I would add tests for <, , ", '.
Agreed. I can add more tests to this one. However, we also need to properly display the test cases so that the user understands what the test is asking. Currently, the test case reads like this: whereas what we need is something like this: ! Anyone have ideas on how to accomplish this?
This was solved in a recent commit. This issue should be closed.
Thank you for your help! We've now fixed this in production as well!

Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. This bonfire seems to be missing assertion tests for all the different test cases outlined in the instructions. It currently is only testing the case of the ampersand (&) and is leaving out the <, , ', and " cases. Suggest adding another assertion or assertions to test the rest of these cases.
Just for logging purposes, this was discussed in . I'm currently not at a computer, but if someone wants to assign me, I could fix this as soon as I can, which /should/ be tonight.