Change:
<!-- 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: Correct answer doesn't get evaluated to true. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: Operating System: Windows 10 Home If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
Hello there, You have not done what the lesson has asked. Whilst your code does cause the styling of the element to be what is expected, the lesson is about , your code is not using inline-styles to style the element, and so should not pass the challenge. As such, I am closing this issue. In general, if you have further questions, I recommend you make use of the I hope this clarifies.
Forum thread: I'm reopening this because I don't really understand the reason given for closing the issue. More importantly, I think we can make it more clear where the object is supposed to be located. That or make the tests accept a class field as well (seems unnecessary to allow both though).
I think that the failing example does use inline styles (at least as I understand it), it just does it in a way that doesn't use the typical pattern (but I have declared and modified inline styles dynamically in the component before). But then we're assuming that the learner is already familiar with the pattern we are trying to teach. Perhaps we could add to the instructions: I was thinking about an example, but it might be too similar to the answer. I think the above addition would make it clear with minimal disruption. Addendum: Sorry, I just read lasjorg's answer - that may be better than my suggestion. I could support either.
I think updating the seed code with the example I posted would be fine. But suggestion might work as well. I'm fine with either really. I was thinking that it seems like a good first-time PR but because issues are not visibly bumped up (can you bump issues?), I'm guessing this issue might be buried too far down. I can label it and see what happens, otherwise, we might just have to do it ourselves.
/assign
Hello, I would like to work on this issue. Can it be assigned to me?
Hello An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the

Discussion:
# --instructions-- <del> If you have a large set of styles, you can assign a style `object` to a constant to keep your code organized. Initialize a `styles` constant and assign an `object` with three style properties and their values to it. Give the `div` a color of `purple`, a font-size of `40`, and a border of `2px solid purple`. Then set the `style` attribute equal to the `styles` constant. </del> <ins> If you have a large set of styles, you can assign a style `object` to a constant to keep your code organized. Declare your styles constant as a global variable at the top of the file. Initialize `styles` constant and assign an `object` with three style properties and their values to it. Give the `div` a color of `purple`, a font-size of `40`, and a border of `2px solid purple`. Then set the `style` attribute equal to the `styles` constant. </ins> # --hints--