- Change invalid CSS to valid CSS
Although today's browsers are becoming more capable of handing errors in CSS, some errors are not always caught gracefully. This variable can make it extremely difficult to apply style or layout consistently. What can be done to quickly scan our CSS documents for issues? Let's practice using the W3C's CSS Validator!
Fork and clone this lesson into your local environment. Navigate into its directory
in the terminal, then run code . to open the files in Visual Studio Code. Finally,
run bundle to install the lab's dependencies. Run rspec to as you go to see your
test progress.
In this lesson, we will be taking the invalid CSS in css/style.css and changing it to valid.
- Open index.html in your browser. Notice how our styles don't look quite right?
- Open css/style.css in your text editor.
- Visit the W3C CSS validator http://jigsaw.w3.org/css-validator/#validate_by_input. If not already selected, click on the tab labeled "By direct input".
- Copy the code from css/style.css and paste it into the text area. Click the "Check" button.
- Use the error messages to correct the CSS.
- Repeat steps 3-5 until your readout states "Congratulations! No Error Found.".
Remember to check your progress in index.html in your browser!
Currently, the work you've done on this assignment is only on your local machine. To preserve work on your GitHub fork, you will need to stage the changes you've made, commit them, and push the commit up to GitHub. Use the following commands to do this:
git add .
git commit -m "Completed assignment"
git pushIf you visit your fork on GitHub, you should now see that you've made the most recent commit, and your solution will be present in the files.
With a CSS validator, you can work your way through cleaning up errors in a CSS document and reduce the likelihood of display errors across platforms. Using the W3C CSS validator will help you quickly and efficiently troubleshoot your CSS.