Bugs in Colored Markers Step 2
See original GitHub issueDescribe the Issue
I am able to pass this step by completely removing all HTML from the editor. I am also able to pass this step if I add the correct head and body elements but delete everything else. Finally, I am able to pass this test if I add the body element before the head element.
Affected Page
Your code
Described above.
Expected behavior
I’m not sure how many of these bugs absolutely need fixing but I would think the empty editor bug should be fixed for sure. And since the instructions ask that the body element be added after the head element we should probably fix that one as well.
Screenshots
No response
System
Confirmed with newest versions of both Chrome and Firefox.
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Colored Markers step 49 · Issue #46351 - GitHub
Describe the Issue After right changing code I face with one problem: "Your .red CSS rule should have a background property with the...
Read more >Colored Markers - Step 4 , Is this a bug? - HTML-CSS
Tell us what's happening: Describe your issue in detail here. It doesn't let me go forward and give me the error: “you can...
Read more >Copic Coloring Guide Level 2: Nature - Amazon.com
Step 7: Add cast shadows and subtle highlights with W3. Sources: White smooth X-Press It Blending Card, markers and Colorless Blender from Imagination ......
Read more >Let's learn CSS colors by building a set of colored ... - YouTube
Let's learn CSS colors by building a set of colored markers ! [Free Webdev Bootcamp]. Watch later. Share. Copy link.
Read more >Learn Basic CSS by Building a Set of Colored Markers
Playlist with all steps : https://youtube.com/playlist?list=PLa-0Y08VoGnrrXojXq95_Ax9GLHBIFbOLWalk through steps 1-10 of the Learn Basic CSS ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I stuck a
console.log(code)in the first test and when there is no content in the editorcodeequals<head></head><body></body>. I don’t know enough about how this works to know why that’s the case, but that explains why it is passing when there is no content in the editor.It also passes
And probably other variations as well. This is with FF 100 on linux. I think browsers are just too good at fixing bad HTML 😄