Scribd
Upload
2 views1 page

Validation: .Audio-Player Ul A

The document discusses basic guidance on debugging HTML and CSS, emphasizing the importance of checking for well-formed code and syntax errors. It highlights common issues that arise from conflicting CSS rules, especially when using third-party code, and suggests strategies like namespacing to avoid conflicts. Additionally, it recommends regular validation of HTML using services like the W3C Markup Validation Service to ensure proper tag usage and structure.

Uploaded by

viniciusteleco
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views1 page

Validation: .Audio-Player Ul A

The document discusses basic guidance on debugging HTML and CSS, emphasizing the importance of checking for well-formed code and syntax errors. It highlights common issues that arise from conflicting CSS rules, especially when using third-party code, and suggests strategies like namespacing to avoid conflicts. Additionally, it recommends regular validation of HTML using services like the W3C Markup Validation Service to ensure proper tag usage and structure.

Uploaded by

viniciusteleco
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

In our Debugging HTML and Debugging CSS articles, we provided some really basic

guidance on debugging HTML/CSS — if you are not familiar with the basics, you should
definitely study these articles before carrying on.
Basically, it is a matter of checking whether your HTML and CSS code is well formed and
doesn't contain any syntax errors.

Note: One common problem with CSS and HTML arises when different CSS rules
begin to conflict with one another. This can be especially problematic when you
are using third party code. For example, you might use a CSS framework and find
that one of the class names it uses clashes with one you've already used for a
different purpose. Or you might find that HTML generated by some kind of third
party API (generating ad banners, for example) includes a class name or ID that you
are already using for a different purpose. To ensure this doesn't happen, you need
to research the tools you are using first and design your code around them. It is
also worth "namespacing" CSS, e.g. if you have a widget, make sure it has a
distinct class, and then start the selectors that select elements inside the widget
with this class, so conflicts are less likely. For example .audio-player ul a .

Validation
For HTML, validation involves making sure all your tags are properly closed and nested, you
are using a doctype, and you are using tags for their correct purpose. A good strategy is to
validate your code regularly. One service that can do this is the W3C Markup Validation
Service , which allows you to point to your code, and returns a list of errors:

You might also like