Эти ошибки так сложно понять, что они означают? Я просмотрел документ несколько раз и решил все проблемы, за исключением этих трех, которые отказываются покинуть меня, но эти ошибки все еще остаются. Может ли кто-нибудь помочь мне понять, что здесь не так, потому что я явно не могу найти на него ответа.
<!DOCTYPE html>
<html lang = "en">
<head>
<meta charset = "utf-8">
<title>Pragerio</title>
<link href = "Index.css" rel = "stylesheet" type = "text/css">
</head>
<body>
<video autoplay = "" loop = "" muted = "" id = "BackgroundVideo">
<source src = "Animatic15.mp4" type = "video/mp4">
</video>
<img class = "logo" src = "Pragerio_Logo.svg" height = "211" id = "PragerioLogo" alt = "Pragerio Logo">
<div class = "grid-container">
<div class = "item1">
<table>
<tr>
<th class = "has-dropdown">
<span class = "title-text">FERA</span>
<div class = "dropdown">
<a href = "FeraAbout.html"><div>About</div></a>
<a href = "FeraCompare.html"><div>Compare</div></a>
<a href = "Order.html"><div>Order</div></a>
</div>
</th>
<th class = "has-dropdown">
<span class = "title-text">SENSAÇÃO</span>
<div class = "dropdown">
<a href = "SensacaoAbout.html"><div>About</div></a>
<a href = "SensacaoCompare.html"><div>Compare</div></a>
<a href = "Order.html"><div>Order</div></a>
</div>
</th>
<th> </th>
<th class = "has-dropdown2">
<span class = "title-text">PRESS</span>
<div class = "dropdown2">
<a href = "News.html"><div>News</div></a>
<a href = "Visits.html"><div>Visits</div></a>
</div>
</th>
<th class = "has-dropdown2">
<span class = "title-text">ABOUT</span>
<div class = "dropdown2">
<a href = "Heritage.html"><div>Heritage</div></a>
<a href = "Contact.html"><div>Contact</div></a>
</div>
</th>
</tr>
</table>
</div>
<div class = "item2">
</div>
<div class = "item3">
<span class = "ctext">Attention</span><br>
<span class = "ctext">2021 © Pragerio, Ltda. and Partners</span><br>
<span class = "ctext">(Name Nameson)</span>
</div>
</div>
</body>
</html>
" Parse Error. Style sheets should not include HTML syntax. <!DOCTYPE HTML> "
"Parse Error <html lang = "en"> <head> <meta charset = "utf-8"> <title>Pragerio</title> <link href = "Index.css" rel = "stylesheet" type = "text/css"> </head> <body> <video autoplay = "" loop = "" muted = "" id = "BackgroundVideo"> <source src = "Animatic15.mp4" type = "video/mp4"> </video> <img class = "logo" src = "Pragerio_Logo.svg" height = "211" id = "PragerioLogo" alt = "Pragerio Logo"> <div class = "grid-container"> <div class = "item1"> <table> <tr> <th class = "has-dropdown"> <span class = "title-text">FERA</span> <div class = "dropdown"> <a href = "FeraAbout.html"><div>About</div></a> <a href = "FeraCompare.html"><div>Compare</div></a> <a href = "Order.html"><div>Order</div></a> </div> </th> <th class = "has-dropdown"> <span class = "title-text">SENSA????O</span> <div class = "dropdown"> <a href = "SensacaoAbout.html"><div>About</div></a> <a href = "SensacaoCompare.html"><div>Compare</div></a> <a href = "Order.html"><div>Order</div></a> </div> </th> <th> "
Parse Error ;</th> <th class = "has-dropdown2"> <span class = "title-text">PRESS</span> <div class = "dropdown2"> <a href = "News.html"><div>News</div></a> <a href = "Visits.html"><div>Visits</div></a> </div> </th> <th class = "has-dropdown2"> <span class = "title-text">ABOUT</span> <div class = "dropdown2"> <a href = "Heritage.html"><div>Heritage</div></a> <a href = "Contact.html"><div>Contact</div></a> </div> </th> </tr> </table> </div> <div class = "item2"> </div> <div class = "item3"> <span class = "ctext">Attention</span><br> <span class = "ctext">2021 ?? Pragerio, Ltda. and Partners</span><br> <span class = "ctext">(Erik Granlund)</span> </div> </div> </body> </html>
Translation of the W3C CSS Validator
The CSS Validation service is currently available in 21 languages. The translations are mainly contributed by volunteers.
Translate the CSS validator in a new language
If the CSS validator is not yet available in your native language and you would like to translate it:
- Download the translation kit. Unpack the kit: It includes a number of HTML documents, a file with all the strings used for the validator messages, and a text files with instructions.
- Get in touch with us before you start translating: someone may already be on the job. Someone from the W3C staff or validator development team will get back to you with details about how to translate the validator.
- Translate. Congratulations, you have made the CSS validator more accessible to a lot more Web developers and designers.
Help complete the translation of the validator in your language
The table below lists all the text strings used to translate the CSS validator:
- Cells marked ✘ need a new or updated translation. Click on the relevant ✘ to submit a translation by mail.
- Cells marked ✔ are translated and up-to-date. Hover above ✔ to read the current translation for each string.
You can help fill the blanks and complete the translation in your language!
Property | Deutsch 80% |
Español 81% |
Français 100% |
한국어 82% |
Italiano 79% |
Nederlands 79% |
日本語 79% |
Polski 90% |
Português 93% |
Русский 84% |
فارسی 77% |
Svenska 97% |
Български 82% |
Українська 80% |
Čeština 80% |
Romanian 80% |
Magyar 78% |
Ελληνικά 78% |
हिन्दी 83% |
简体中文 86% |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
about
About |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
about_title
About this service |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
address
Address |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
all
All |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
ATSC_TV_profile
ATSC TV profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
aural
aural |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
braille
braille |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
by_direct_input
By direct input |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
by_file_upload
By file upload |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
by_URI
By URI |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
check
Check |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
check_CSS
Check Cascading Style Sheets (CSS) and (X)HTML documents with style sheets |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
choose_document
Choose the document you would like validated |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
choose_local_file
Choose a Local File to Upload and Validate |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
congrats
Congratulations! No Error Found. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
content-language
en |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
content-type
text/html; charset=utf-8 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
credits
Credits |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
credits_title
Credits and Acknowlegments |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
css1
CSS level 1 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
css2
CSS level 2 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
css21
CSS level 2.1 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
css3
CSS level 3 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
css3svg
CSS Level 3 + SVG |
✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
css_doc
CSS |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
CSS_not_found
No style sheet found |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
CSS_validation_service
CSS validation Service |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
direction
ltr |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
dl
Download |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
dl_title
Download and install the CSS validator |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
doc
Documentation |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
doc_title
Documentation for the W3C CSS Validation Service |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
doc_validates_after_link
! |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
doc_validates_before_link
This document validates as |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
embossed
embossed |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
enter_CSS
Enter the CSS you would like validated |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
enter_uri
Enter the URI of a document (HTML with CSS or CSS only) you would like validated |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.angle
“%s” is not a valid angle. Value should be between “0” and “360” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.anglevalue
Value must be between “-360” and “360” and be divisable by “90” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.at-rule
Unrecognized at-rule “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.attr
Invalid attr definition attr(X) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.bg_order
In the CSS3 background definition, “bg_position” must occur before / “bg_size” if both are present |
✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ |
error.colorfunc
“%s1” is not a valid %s2 color |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.comma
Missing comma separator. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.comparator
The “%s” and “%s” comparators are not compatible in a media feature of type “range” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.conflicting-charset
Conflicting charset definition between network and @charset “%s” and “%s” charset |
✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.counter
Invalid counter definition counter(<identifier>[,<list-style-type>]?) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.counters
Invalid counters definition counters(<identifier>,<string>[,<list-style-type>]?) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
error.degree
Position must be described in terms of degrees. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.deprecatedmedia
The media “%s” has been deprecated |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.deprecatedmediafeature
Deprecated media feature “%s”. For guidance, see the Deprecated Media Features section in the current Media Queries specification. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.divisortype
The divisor must be a number |
✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.divzero
Division by zero |
✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.elevation.range
Specifies the elevation as an angle, between “-90deg” and “90deg’. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.email
email addresses cannot be validated by this tool, you might be scammed |
✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.emptymedia
In CSS2, the media type in @media is mandatory |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.errortoken
Unexpected content “%s” at line “%s”, expecting on token of “%s” (skipped “%s”) |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.few-value
too few values for the property “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.format
Invalid format definition format(<string>[,<string>]*) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.function
Invalid function definition |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
error.generic-family.quote
Generic family names are keywords, and therefore must not be quoted. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.greater
“%s” is not valid, only values strictly greater than “%s” are allowed. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.greaterequal
“%s” is not valid, only values greater than or equal to “%s” are allowed. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.grid
Only “0” and “1” are acceptable values for grid |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ |
error.groupname
“%s” is not a correct groupname. Use a valid identifier |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.id
ID selector #%s is invalid ! Only one ID selector can be specified in a simple selector: %s. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.incompatible
“%s” and “%s” are incompatible |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.incompatibletypes
The types are incompatible |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.integer
This number should be an integer. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.invalid-color
Invalid RGB function |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.invalidtype
Invalid type: “%s” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.linear-gradient-missing-to
The first argument to the “linear-gradient” function should be “%s”, not “%s” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
error.local
Invalid format definition local(<string>|<ident>+) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.lower
“%s” is not valid, only values strictly lower than “%s” are allowed. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.lowerequal
“%s” is not valid, only values lower than or equal to “%s” are allowed. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.media
unrecognized media “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.negative-value
“%s” negative values are not allowed |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.noatruleyet
Other @rules than @import are not supported by CSS1 “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.nocomb
Combinator “%s” between selectors is not allowed in this profile or version |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.noexistence
Property “%s” doesn’t exist in “%s” but exists in “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.noexistence-at-all
Property “%s” doesn’t exist |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.noexistence-media
Feature “%s” doesn’t exist for media “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.noexistence-typo
Property “%s” doesn’t exist. The closest matching property name is “%s” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.nogroup
“%s” has not been set by the “toggle-group” property |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
error.nomediafeature
Media features are not defined in this CSS level |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.nomediarestrictor
Mediarestrictor not defined in this CSS level |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.nomodifiermedia
The media feature “%s” does not support prefixes |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ |
error.nomodifierrangemedia
No prefixes are allowed for range media features |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.nomodifiershortmedia
No prefixes are allowed for media features with no value |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ |
error.notforatsc
“%s” can not be used with ATSC profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.notforcss1
Value “%s” does not exist for CSS1 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.notformobile
“%s” can not be used with mobile profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.notfortv
“%s” can not be used with TV profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.notversion
“%s” can not be used with this version of CSS : “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.onlyATSC
“%s” this function is only for the atsc-tv medium |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.operandnumber
One operand must be a number |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
error.operator
“%s” is an incorrect operator |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.page
unrecognized pseudo named page “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.percent
“%s” is an incorrect percentage |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.percentage
percentage value expected |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.pseudo
Unknown pseudo-element or pseudo-class “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.pseudo-class
The pseudo-class .“%s” can’t appear here in the HTML context “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.pseudo-element
The pseudo-element “%s” can’t appear here in the context “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.pseudo-element-not-last
The selector “%s” can’t appear after the pseudo-element selector “%s” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.range
The value is out of range.This value must be between “0” and “100”’. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.rgb
“%s” is not a valid color 3 or 6 hexadecimals numbers |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.same-value
“%s” appears twice |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.selectorname
Invalid selector name “%s” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
error.shape
Invalid shape definition rect(<top>,<right>,<bottom>,<left>) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.shape-separator
Invalid separator in shape definition. It must be a comma. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.space
If the attribute selector ~= is used, the word in the value “%s” must not contain spaces. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.strictly-positive
“%s” is not valid, only values greater than “0” allowed. |
✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✔ | ✔ |
error.string
“%s” is an incorrect string |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.system-font-keyword-not-sole-value
No other property values should be used with “%s”. It should be the sole value; e.g., “p { font: %s; }” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
error.todo
Sorry the feature “%s” is not implemented yet. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.two-lengths
A shadow offset is specified with two <length> values (A blur radius may optionally be specified after the shadow offset.) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.typevaluemismatch
The value “%s” is incompatible with its type definition <“%s”> |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
error.unit
“%s” is an incorrect unit |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.unknown
Unknown error |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.unrecognize
Too many values or values are not recognized |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
error.unrecognized.link
Unrecognized link element or xml-stylesheet PI. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.url
“%s” is an incorrect URL |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.value
“%s” is not a “%s” value |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
error.zero
only “0” can be a “%s”. You must put a unit after your number |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
errors
Errors |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
errors_sorry_msg
Sorry! We found the following errors |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
feedback
Feedback |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
feedback_title
How to provide feedback on this service |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.context
Context |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.doc
<!— removed this confusing message olivier 2006-12-14 —> |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.doc-html
<!— removed this confusing message olivier 2006-12-14 —> |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.dontmixhtml
Parse Error. Style sheets should not include HTML syntax. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
generator.invalid-number
Invalid number |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.line
Line |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.not-found
File not found |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.property
Value Error |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.request
An error occured during the output of your style sheet. Please correct your request or send a mail to plh@w3.org. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.unrecognize
Parse Error |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
generator.unrecognized
Unrecognized |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
handheld
handheld |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
home
Home |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
home_title
Home page for the W3C CSS Validation Service |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
html_doc
HTML |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
jump_to
Jump to |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
language_name
English |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
learn_more_msg
Learn more about Cascading Style Sheets |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
local_CSS_file
Local CSS file |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
medium
Medium |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
mobile
Mobile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
more_options
More Options |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
most_important
Most important |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_errors_bookmark_msg
Or, you can just add the current page to your bookmarks or hotlist. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_errors_close_tags_msg
close the img tag with > instead of /> if using HTML <= 4.01 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_errors_create_link_msg
If you would like to create a link to this page (i.e., this validation result) to make it easier to re-validate this page in the future or to allow others to validate your page, the URI is: |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_errors_dl_local_msg
If you like, you can download a copy of this image to keep in your local web directory, and change the XHTML fragment above to reference your local image rather than the one on this server. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_errors_forHTML_only_msg
for HTML/XML document only |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
no_errors_interoperable_msg
To show your readers that you’ve taken the care to create an interoperable Web page, you may display this icon on any page that validates. Here is the XHTML you could use to add this icon to your Web page: |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_special_profile
No special profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_special_type
Automatic |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
no_warnings
No warnings |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
normal_report
Normal report |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
not-css1-style
/* BE CAREFUL ! This is not a CSS1 property ! */ |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
note
Note |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
note_valide_html
To work as intended, your CSS style sheet needs a correct document parse tree. This means you should use <a href=»http://validator.w3.org/»>valid HTML</a>. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
note_xhtml_valid
If you want to validate your CSS style sheet embedded in an (X)HTML document, you should first <a href=»http://validator.w3.org/»>check that the (X)HTML you use is valid</a> |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
output-encoding-name
utf-8 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
page_address
Address of page to Validate |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.attrcss1
Attribute selectors are invalid in CSS1 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
parser.calcwhitespace
Whitespace is required on both sides of the “+” or “-” operators |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
parser.charset
The @charset rule may only occur at the start of the style sheet. Please check that there are no spaces before it. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.charsetcss1
@charset rules can not be used in CSS1 |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.charsetspecial
This profile has a very specific syntax for @charset: @charset followed by exactly one space, followed by the name of the encoding in quotes, followed immediately by a semicolon. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.class_dim
In CSS1, a class name can start with a digit («.55ft»), unless it is a dimension («.55in»). |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.id_dim
In CSS1, an id name can start with a digit («#55ft»), unless it is a dimension («#55in»). |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.import_not_allowed
@import are not allowed after any valid statement other than @charset and @import. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✔ | ✔ |
parser.invalid_id_selector
Invalid ID selector |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✔ | ✔ |
parser.old_class
In CSS1, a class name could start with a digit («.55ft»), unless it was a dimension («.55in»). In CSS2, such classes are parsed as unknown dimensions (to allow for future additions of new units) To make “%s” a valid class, CSS2 requires the first digit to be escaped: “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.old_id
In CSS1, an id name could start with a digit («#55ft»), unless it was a dimension («#55in»). In CSS2, such ids are parsed as unknown dimensions (to allow for future additions of new units) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.semi-colon
Missing a semicolon before the property name “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
parser.unknown-dimension
Unknown dimension |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
presentation
presentation |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
print
|
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
profile
Profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
projection
projection |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
screen
screen |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
servlet.invalid-request
You have sent an invalid request. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
servlet.process
Can’t process the object |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
submit_file
Submit file for validation |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
submit_input
Submit your input for validation |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
submit_uri
Submit URI for validation |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
support
Support this tool, become a |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
supporter
W3C Supporter |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
svg
SVG |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
svgbasic
SVG Basic |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
svgtiny
SVG tiny |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
title_more_options
Show/Hide extra validation options |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
top
Top |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
tty
TTY |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
tv
TV |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
TV_profile
TV profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
type
Type |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
valid_CSS
Valid CSS! |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
valid_CSS_info
Valid CSS information |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
validate_by_file_upload
Validate by file upload |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
validate_by_input
Validate by direct input |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
validate_by_URI
Validate by URI |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
validated_CSS
Validated CSS |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
vendorext
Vendor Extensions |
✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ |
vext_default
Default |
✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ |
vext_errors
Errors |
✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ |
vext_warnings
Warnings |
✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ |
W3C_CSS_validation_service
The W3C CSS Validation Service |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
W3C_quality_msg
W3C’s Quality Assurance Activity, bringing you free Web quality tools and more |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
W3C_validator_results
W3C CSS Validator results for |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.at-rule
Unrecognized at-rule “%s” |
✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.atsc
“%s” might not be supported by the medium atsc-tv |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
warning.block-level
This property applies to block-level elements. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.body-inside
BODY element can’t be inside another element except HTML |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.charsetspecial
This profile has a very specific syntax for @charset: @charset followed by exactly one space, followed by the name of the encoding in quotes, followed immediately by a semicolon. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.comparator
Comparators “%s” and “%s” are the same, one of them will be ignored |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.css-hack
“%s” is a CSS hack |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.css-variable
Due to their dynamic nature, CSS variables are currently not statically checked |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.deprecated
The value “%s” is deprecated |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.deprecated_replacement
The value “%s1” is deprecated, use “%s2” instead |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.deprecatedmedia
The media “%s” has been deprecated |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.deprecatedmediafeature
Deprecated media feature “%s”. For guidance, see the Deprecated Media Features section in the current Media Queries specification. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.deprecatedproperty
The property “%s” is deprecated |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.direction
instead of using “direction” for block-level elements use the new CSS3 “writing-mode” property |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
warning.dynamic
dynamic values cannot be checked as an unitless number. Please qualify it with an unit. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.float-no-width
In (x)HTML+CSS, floated elements need to have a width declared. Only elements with an intrinsic width (html, img, input, textarea, select, or object) are not affected |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.greaterequal
value “%s” will be interpreted as “%s” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.html-inside
HTML element can’t be inside another element |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.incompatible
“%s” and “%s” are incompatible |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.link-type
You should add a “type” attribute with a value of “text/css” to the “link” element |
✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ |
warning.lowerequal
value “%s” will be interpreted as “%s” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.marker
The “marker-offset” property applies on elements with “display: marker” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.medialist
medialist should start with “media:” “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.negative
negative value “%s” will be interpreted as “0” |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
warning.no-background-color
You have no background-color set (or background-color is set to transparent) but you have set a color. Make sure that cascading of colors keeps the text reasonably legible. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.no-color
You have no color set (or color is set to transparent) but you have set a background-color. Make sure that cascading of colors keeps the text reasonably legible. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
warning.no-declaration
No declarations in the rule |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.no-generic-family
“%s”: You are encouraged to offer a generic family as a last alternative |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.no-padding
You are encouraged to have a padding area with a background color |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.nocomb
Combinator “%s” between selectors is not allowed in this profile (“%s”) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.noexistence
Property “%s” doesn’t exist in “%s” but exists in “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.noexistence-media
Property “%s” doesn’t exist for media “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.noexproperty
Property “%s” does not exist |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ |
warning.noinside
“%s” can’t be inside an inline element |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.noothermedium
Properties for other media might not work for usermedium |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.notforusermedium
Property “%s” doesn’t exist for this usermedium |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.notversion
“%s” can not be used with this version of CSS : “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.old_class
In CSS1, a class name can start with a digit («#55ft»), unless it is a dimension («#55in»). In CSS2, such ids are parsed as unknown dimensions (to allow for future additions of new units). |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
warning.old_id
In CSS1, an id name can start with a digit («#55ft»), unless it is a dimension («#55in»). In CSS2, such ids are parsed as unknown dimensions (to allow for future additions of new units) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.otherprofile
property “%s” does not exist for this profile, but is validated conforming to another profile |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.out-of-range
“%s” is out of range |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.pseudo
Unknown pseudo-element or pseudo-class “%s” in the default profile (“%s”) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.pseudo-classes
Anchor pseudo-class “%s” have no effect on elements other than “A’ |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.redefinition
Redefinition of “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.relative
Using relative units gives more robust stylesheets in property “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.relative-absolute
You have some absolute and relative lengths in %s”. This is not a robust style sheet. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.same-colors
Same color for “%s” and “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.same-colors2
Same colors for color and background-color in two contexts “%s” and “%s” |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.shape-separator
Invalid separator in shape definition. It must be a comma. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.space
If the attribute selector ~= is used, the word in the value “%s” should not contain spaces. |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
warning.style-inside-comment
Do not put style rules inside HTML comments as they may be removed by user agent |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.unknown-html
“%s” is not an HTML Element |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.unsupported-import
Imported style sheets are not checked in direct input and file upload modes |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.value-unofficial
“%s” is not defined by any specification as an allowed value for “%s”, but is supported in multiple browsers |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.vendor-ext-pseudo-class
“%s” is an unknown vendor extended pseudo-class |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.vendor-ext-pseudo-element
“%s” is an unknown vendor extended pseudo-element |
✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
warning.vendor-extension
“%s” is an unknown vendor extension |
✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✔ | ✘ |
warning.with-space
Family names containing whitespace should be quoted. If quoting is omitted, any whitespace characters before and after the name are ignored and any sequence of whitespace characters inside the name is converted to a single space. |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.withblock
Be careful. Pseudo-elements can only be attached to a block-level element |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.xsl
value “%s” only applies to XSL |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warning.zero
only “0” can be a “%s”. You must put a unit after your number |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
warnings
Warnings |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Property | Deutsch | Español | Français | 한국어 | Italiano | Nederlands | 日本語 | Polski | Português | Русский | فارسی | Svenska | Български | Українська | Čeština | Romanian | Magyar | Ελληνικά | हिन्दी | 简体中文 |
-
Юбилейный DevConfX пройдет 21-22 июня в Москве. Как всегда — Вы решаете, кто попадет в программу секции Backend — голосуйте за интересные доклады
-
Автор темы
Mishcka
-
Дата начала
2 Сен 2010
- Статус
- В этой теме нельзя размещать новые ответы.
-
#1
Ужаснейшая и очень грустная ошибка Parse error: syntax error, unexpected $end
Ужаснейшая и очень грустная ошибка Parse error: syntax error, unexpected $end
Превед, робяты! Возникла непредвиденная ошибка:
Parse error: syntax error, unexpected $end in /home/vhosts/plotnikova.com/wp-admin/includes/update.php on line 48.
Кто знает что за фигня?
Вот код:
<?php
$local_package = isset( $wp_local_package ) ? $wp_local_package : »;
?>
-
#2
закрывающая фигурная скобка где-то забыта
-
#5
Автор оригинала: Adelf
закрывающая фигурная скобка где-то забыта
Ага, только я не пойму где
Я гуглил сначала — не помогло, именно поэтому я обратился в этот форум.
Автор оригинала: zerkms
ну и phpfaq.ru/debug
На фиг мне отладчик — я знаю что за ошибка, но не в курсе как ее исправить
-~{}~ 02.09.10 07:26:
Я отредактировал сообщение и оставил в коде только строку с ошибкой.
-
#6
http://phpclub.ru/paste приведи весь код.
-
#7
если ты знаешь что за ошибка, то почему не указал её в коде? в приведённой строке этой ошибки нет.
-
#8
Автор оригинала: zerkms
если ты знаешь что за ошибка, то почему не указал её в коде? в приведённой строке этой ошибки нет.
Но где-то там.
-~{}~ 02.09.10 08:39:
-
#9
увы, но эта ошибка не из-за этой строки. моя ссылка про осмысление процесса отладки всё таки в силе. читай.
-
#10
Ошибки
> syntax error, unexpected $end
В приведенном тобой коде нет.
-~{}~ 02.09.10 14:05:
Скорее всего, твой файл тупо не залился по FTP полностью
-~{}~ 02.09.10 14:05:
Сравни размеры.
-
#11
Автор оригинала: Активист
Сравни размеры.
Заливал уже файл раз 5. Сравнил размеры — совпадают. Мракобесие
-
#12
Mishcka
прямо на хосте отлаживай.
для таких ошибок подходит метод постепенного сокращения кода.
удаляешь блоки кода до тех пор, пока ошибка не станет видна
-
#13
Mishcka
Для таких как ты, сделали подсветку ошибок в IDE, ты в чем пишешь код?
-
#14
Автор оригинала: c0dex
Mishcka
Для таких как ты, сделали подсветку ошибок в IDE, ты в чем пишешь код?
У меня есть подсветка в Rapid PHP 2010.
Я подсчитал количество открывающих и закрывающих фигурных и обычных скобок — количества совпадают.
-~{}~ 02.09.10 16:08:
Автор оригинала: *****
Mishcka
прямо на хосте отлаживай.
для таких ошибок подходит метод постепенного сокращения кода.
удаляешь блоки кода до тех пор, пока ошибка не станет видна
Ага, я уже удалил все строки из этого файла, он занимает 0 байт, НО ошибка осталась и по-прежнему на 48-й строке, похоже пора отдохнуть и пить успокаивающее
-
#15
обячная хрень, отлаживаешь одно, а работает другое.
там часом никаких акселераторов нет, которые могли бы закешировать код?
-
#16
Автор оригинала: dimagolov
обячная хрень, отлаживаешь одно, а работает другое.
там часом никаких акселераторов нет, которые могли бы закешировать код?
Не знаю что это и не знаю как узнать стоит или нет.
-
#17
dimagolov
Вот уж не думал, что человек, добравшийся до уставновки какого-нибудь акселератора, стал бы писать тут такое.
Mishcka
Подсветка ошибок есть красным цветом?
-
#18
еще в опере есть свойство, что если сервер отдает пустую страницу(в том числе и с кодом 500), либо вообще не резолвится, то она упорно показывает предыдущий успешный результат — т.е. страницу с текстом ошибки, если только не было передано no-cache.
-
#19
обычно такая фигня когда заливаешь файл в рабочую систему, то есть пока файл копируется кто-то к нему обратился, к недокаченному
-
#20
berkut
Засунул в IDE, ошибок не обнаружил, но apache отдал 500 ошибку, Undefied Function в контенте, FireFox показал 500 ошибку))
Скорее в этои и есть проблема, юзай Firefox =)
- Статус
- В этой теме нельзя размещать новые ответы.
With a bit of help, you can always establish and eradicate a CSS parse error whenever it happens.
CSS provides a powerful way of styling websites, reducing web page load times, and saving precious time for developers. However, you need to know how to handle a CSS parse error. Read on to find out how.
What Is a Parse Error in CSS?
The parse error in CSS arises when the CSS parser detects something that does not comply with the requirements. Usually, a CSS parser demands CSS be written in a certain way.
CSS parser has specific requirements that include:
- Adding a semicolon at the end of all CSS properties
- One ruleset cannot contain the same CSS property twice
- All rules require both opening and closing curly brackets ({})
- All quotes should be closed
Ways to Minimize Cases of CSS Parse Error
There are ways of keeping your style sheets pristine for both your clients and designs. Having a clean CSS file makes it easy to implement your design ideas without delays. Below are some of the approaches you can use to avoid parsing errors in CSS.
1. Use frameworks
Like icons in the fashion industry set the tone for what is trending, trendsetters in tech influence the styling of thousands of websites. You may wonder how this happens. Well, developers build and publish frameworks which are a set of rules for the common website elements.
The frameworks offer you and other developers a good starting point for web design. They help you design a decent website fast. With a framework, you get a reliable base that you experiment with, like tweaking fonts and colors.
2. Seek simplicity
As the website grows, you will find yourself scrolling through a long list of CSS elements and rules. The rules may override each other in some cases, but eventually, the most specific rule will always win.
You may end up with more code than anticipated, especially when accounting for different screen sizes and browsers. So, it is good practice to always establish before including new style rules; perhaps the existing ones could work.
3. Structure your CSS file
You have various ways of refactoring your CSS code to ease use and navigation. Some of the most straightforward approaches are the most effective. These include:
- Uniform spacing between rules as well as in declarations across the CSS file to make it easy to read.
- Capitalize on semantic or familiar id/class names. For instance, avoid a class name such as “bottom_menu” instead use the semantic tag “footer.”
- Avoid repeating yourself. You should repeat as little code as possible. If some declaration is repeated across the file, consider typing it once and using various selectors.
- Test the CSS code using online tools that parse the file to highlight problem areas and show any parse error message. These tools are useful in pinpointing specific elements and experimenting with various styles.
4. Use advanced CSS
For someone with some programming skills, advanced CSS options like LESS or SASS are recommended. These let you take advantage of complex code options such as functions, nesting, and variables. The approach helps you clean your code and avoid parsing errors.
Rules for Dealing With CSS Parsing Errors
In most cases, a user agent ignores the illegal part of a style sheet. The user agent accomplishes this by parsing the illegal part to establish where it starts and ends. However, it acts as if the illegal part does not exist. User agents obey the following rules once they come across the scenarios below:
– Unknown Properties
The user agent should overlook a declaration with an unknown property. The user agent is going to consider only the part with known properties.
For example:
h1 { color: red; rotation: 70minutes}
The user agent will treat the style sheet as
– Malformed declarations
The user agents should be able to handle tokens they encounter as they parse declarations to the end. They must do this while correctly managing escapes and paying attention to rules on matching pairs of {}, [], (), ‘’, and “”. For instance, a malformed declaration may miss a property value, colon, or property name.
Failure to pair each properly will prompt a CSS parse error. In some cases, the user agent anticipates the beginning of a declaration or at-rule but finds an unexpected token. In such cases, the token is taken to be the first malformed declaration. That token is used to establish which tokens to overlook.
– Illegal values
The user agent should overlook a declaration containing an illegal value. A CSS parser will honor the first rule then ignore the rest. A user agent meeting CSS specifications can accept one or more rules.
– At-Rules Without Known At-Keywords
A user agent will ignore an invalid at-keyword alongside everything that follows it. It ignores everything until the end of the block with the invalid at-keyword or the next semicolon.
– Unexpected End of Style Sheet and String
A user agent should close all the open constructs at the end of the style sheet. These include parentheses, blocks, comments, strings, brackets, and rules. After reaching the end of a line, the user agent must close the string. Failure to terminate all the constructs properly throws a parse error message.
How to Fix a Parse Error in CSS
When you get parse errors as you copy CSS from a different source, you first need to check the final semicolon. The easiest way to fix these errors is to paste the CSS code into an editor like Notepad++. You can use the editor to find or replace these errors.
You can start by replacing all instances of a semicolon curly bracket with a curly bracket. Also, search for “;s” and replace it with “}}}” to avoid bothering with empty rules like {}. The search will show both ;} and ; }. You can then replace }}} with ;} to ensure your CSS rules have the right closing bracket.
To fix parse errors in CSS, review your custom CSS code. Look out for errors like a missing semicolon, curly brackets, or spelling mistakes in CSS properties. Usually, CSS parsing errors arise from one or several errors in custom CSS. After locating the issue in your custom CSS code, make the right changes, save and refresh to resolve the parse error message.
– CSS Parse Error Handling
CSS is resilient and tries very hard to accomplish what you want even when there is an error. Once it establishes an error in one line, it progresses to the next without any error. Sometimes, it is hard to confirm there is a parse error in your style sheet since the browser does not tell. That’s where online CSS validators come in to establish parsing errors in CSS code.
Common CSS Errors Besides Parse Error
No matter your experience, mistakes such as typos or an incorrectly closed tag in CSS are common. Below are the common errors in CSS.
– Forgotten details
With CSS, you can be as creative as possible, but there are some ground rules to follow. Each selector should be as a class or ID, provided it is not HTML TAG. The selector format should be appropriate with braces, property, value, colon, and semicolon.
If you miss one of the little details, strange things will happen, or the intended output will not be visible. CSS validators let you catch the little forgotten details.
– Missed spellings
Missed spelling errors are some of the most common errors in CSS and are easy to ignore. For instance, “left” is different from “left” in CSS and could be the difference between placing something on the right or the left side of your page.
– Multiple Choice
CSS will choose which one to use if the same selector has two references with conflicting information in your CSS code. It is common when you are adding your style sheet to another one. If nothing is happening for a specific selector, search the style sheet for another reference associated with the selector.
– Wrong Selector
Placing your wonderful designs inside the #content when they should be in #context-text will not help your layout. Fortunately, you can easily see these after viewing the page. So, you only need to cut and paste the code in the correct tag.
Conclusion
In this guide, we’ve covered various aspects of CSS parse errors. Here is a summary of what you need to handle these parsing errors:
Parse error in CSS occurs when a style sheet departs from the precise CSS parser requirements
- Common causes include missing a semicolon, curly brackets, or unknown properties
- With a bit of help from online CSS validators, you can easily catch and fix the error
- Check the line with the parse error and change the code accordingly
Parsing errors in CSS are common but are easy to fix when you know where to look. With this guide, you can indulge your creativity in CSS, knowing you can handle CSS parse errors thrown at you.
- Author
- Recent Posts
Position Is Everything: Your Go-To Resource for Learn & Build: CSS,JavaScript,HTML,PHP,C++ and MYSQL.
Разбор ошибок валидации сайта
Наконец-то появилось свободное время между бесконечной чередой заказов, и я решил заняться своим блогом. Попробуем его улучшить в плане валидации. Ниже в статье я расскажу, что такое валидация сайта, кода html и css, зачем она нужна и как привести сайт к стандартам на конкретном примере.
Что такое валидация сайта?
Простыми словами – это проверка на соответствие стандартам. Чтобы любой браузер мог отображать ваш сайт корректно. Большое влияние валидность сайта на продвижение не оказывает, но хуже точно не будет.
Конкретный пример прохождения валидации для страницы сайта
Возьмем первую попавшуюся страницу на моем сайте — Кодирование и декодирование base64 на Java 8. Забьем адрес страницы в валидатор и смотрим результат:
Errors found while checking this document as HTML 4.01 Transitional! Result: 105 Errors, 67 warning(s)
Да уж, картина вырисовывается неприятная: больше сотни ошибок и 67 предупреждений – как вообще поисковики индексируют мой блог, и заходят люди? Но не будем огорчаться, а научимся проходить валидацию, справлять ошибки. Итак, первое предупреждение:
Unable to Determine Parse Mode! The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because: the MIME Media Type (text/html) can be used for XML or SGML document types No known Document Type could be detected No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document. No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document. As a default, the validator is falling back to SGML mode. Warning No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type. No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax. The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Это одно и тоже. А исправляется просто: в самом начале страницы добавить тег:
<!DOCTYPE html>
Проверяем ,что у нас получилось и видим, что одним этим тегом мы убрали 105 ошибок и 3 предупреждения! Теперь у нас осталось только 64 предупреждения. Начинаем разбирать их по одному.
Warning: The type attribute for the style element is not needed and should be omitted. From line 5, column 1; to line 5, column 23 /x-icon">↩<style type="text/css">↩↩↩↩A
Это значит, что для элемента style не нужен атрибут type – это лишнее. На странице у нас два таких замечания. Аналогичное предупреждение и по JavaScript:
Warning: The type attribute is unnecessary for JavaScript resources. From line 418, column 1; to line 418, column 31 </script>↩<script type="text/javascript">↩$(doc
Таких у нас 8 ошибок. Убираем данные атрибуты и ура – еще на 10 предупреждений меньше!
Error: CSS: background: The first argument to the linear-gradient function should be to top, not top. At line 39, column 61 0%,#E8E8E8 100%);↩ border-r
Следующая ошибка — первый аргумент у linear-gradient должен быть to top, а не top. Исправлем. Далее ошибка:
Error: CSS: Parse Error. From line 65, column 13; to line 65, column 16 margin: 0 auto;↩padd
Здесь у меня неверно закомментировано css. Надо просто убрать эту строку. Или закомментировать по-другому /* и */. Я так сделал, как привык так комментировать на Java.
Error: CSS: @import are not allowed after any valid statement other than @charset and @import.. At line 88, column 74 0,600,700,300);↩@import url(//
Теперь у нас идет ошибка импорта. Перенесем эти строчки в самое начало файла и она исчезнет.
Error: Bad value _blanck for attribute target on element a: Reserved keyword blanck used. From line 241, column 218; to line 241, column 295 cookies. <a href="//upread.ru/art.php?id=98" target="_blanck" style="display: inline;">Здесь
Далее не нравится значение атрибута target, нам сообщают, что надо использовать «blank» без нижнего подчеркивания спереди. Убираем.
Error: End tag li seen, but there were open elements. From line 379, column 2; to line 379, column 6 <ul>↩ </li>↩↩</ul
Теперь у нас идет div не на месте.
Error: Table columns in range 2…3 established by element td have no cells beginning in them. From line 262, column 5; to line 263, column 94 px;">↩<tr>↩<td colspan="3" style="width:100%; padding-bottom: 25px;padding-top: 0px; text-align:center;">↩<img
Следующая ошибка – лишний colspan у ячейки. В моем случае таблица состоит всего из одной ячейки, видимо, забыл убрать, когда менял дизайн. Теперь это и делаем.
Error: Element style not allowed as child of element div in this context. (Suppressing further errors from this subtree.) From line 486, column 1; to line 486, column 7 ↩</table>↩<tyle>↩.hleb Contexts in which element style may be used: Where metadata content is expected. In a noscript element that is a child of a head element. In the body, where flow content is expected. Content model for element div: If the element is a child of a dl element: one or more dt elements followed by one or more dd elements, optionally intermixed with script-supporting elements. If the element is not a child of a dl element: Flow content.
А эта ошибка говорит о том, что нельзя вставлять style внутри div. Переносим в начало файла.
Error: The width attribute on the table element is obsolete. Use CSS instead. From line 505, column 1; to line 505, column 21 >↩↩↩↩↩↩↩↩↩<table width ="100%">↩<tr>↩
Тут нам подсказывают, что не стоит устанавливать ширину атрибутом, а лучше сделать это отдельным тегом. Меняем на style=»width:100%;».
Error: Duplicate attribute style. At line 507, column 41 ign="top" style="padding-right
Переводим: дублируется атрибут style. Второй стиль при этом работать не будет. Объединяем
Error: Attribute name not allowed on element td at this point. From line 506, column 5; to line 507, column 82 0%;">↩<tr>↩<td style="width:1%;padding-right:10px;" valign="top" name="navigid" id="navigid">↩↩↩↩</ Attributes for element td: Global attributes colspan - Number of columns that the cell is to span rowspan - Number of rows that the cell is to span headers - The header cells for this cell
У ячейки не должно быть имени – атрибута name. Тут в принципе можно убрать, id вполне хватит.
Error: The valign attribute on the td element is obsolete. Use CSS instead. From line 506, column 5; to line 507, column 67 0%;">↩<tr>↩<td style="width:1%;padding-right:10px;" valign="top" id="navigid">↩↩↩↩</
Убираем valign. Вместо него ставим style=»vertical-align:top».
Error: & did not start a character reference. (& probably should have been escaped as &.) At line 543, column 232 при lineLength &t;= 0) и lineS
А эта ошибка вообще непонятно как оказалась ) Это я коде к статье ошибся. Меняем на <
Error: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images. From line 654, column 1; to line 654, column 30 /><br />↩<img src="img/art374-1.jpg" />↩<br /
У изображений должен быть alt. Добавляем альты с описанием картинок.
Error: CSS: padding: only 0 can be a unit. You must put a unit after your number. From line 260, column 18; to line 260, column 19 dding: 10 20;↩}↩↩#
Только ноль может быть без обозначений. Надо поставить что – это пиксели, или к примеру, проценты. Добавляем px после чисел.
Warning: The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment. At line 974, column 8 ipt> ↩↩↩ <!--детектим адблок
Не нравятся комментарии. Да, в общем, их можно и убрать, не разбираясь, не особенно они и нужны.
Error: Stray end tag td. From line 982, column 1; to line 982, column 5 ↩</table>↩</td>↩↩<sty
Заблудившийся тег td. Убираем его.
Error: Bad value for attribute action on element form: Must be non-empty. From line 1102, column 6; to line 1102, column 98 /h6>↩ <form action="" id="jaloba-to-me" class="submit" method="POST" accept-charset="windows-1251"> <tabl
Здесь валидатор не устраивает пустое значение атрибута action – должен быть адрес страницы какой-то. У нас обрабатывается данная форма js, так что без разницы, поставим action=”self”
Все! Смотрим результат:
Нет ошибок или предупреждений, страница полностью валидна.
Если вам что-то непонятно в статье или вы хотите, чтобы ваш сайт полностью соответствовал спецификации и стандартам HTML ,вы можете обратиться ко мне. Я проверю и устраню любые шибки валидации.
Автор этого материала — я — Пахолков Юрий. Я оказываю услуги по написанию программ на языках Java, C++, C# (а также консультирую по ним) и созданию сайтов. Работаю с сайтами на CMS OpenCart, WordPress, ModX и самописными. Кроме этого, работаю напрямую с JavaScript, PHP, CSS, HTML — то есть могу доработать ваш сайт или помочь с веб-программированием. Пишите сюда.
заметки, сайтостроение, html, валидация
Содержание
- HTML Checking for Large Sites
- CSS: Parse Error.
- Related W3C validator issues
- Как проверить HTML валидацию сайта — основные ошибки
- Разделы блога
- Как проверить сайт на валидность HTML кода
- Заключение
- Сергей Моховиков
HTML Checking for Large Sites
Rocket Validator integrates the W3C Validator HTML checker into an automated web crawler.
CSS: Parse Error.
CSS styles could not be parsed, check the indicated line to find what caused the parser to fail. Common causes are unclosed curly brackets or comments, missing semicolons or unexpected or empty properties.
A CSS definition for background-image could not be understood by the parser. Check its definition to ensure that it’s well formed and that it contains an appropriate value.
A CSS definition for an X property could not be understood by the parser. Check it to ensure that it’s well formed and that it contains an appropriate value.
The element does not accept a height attribute. Use CSS instead.
The value on the display property is not valid.
The display CSS property sets whether an element is treated as a block or inline element and the layout used for its children, such as flow layout, grid or flex.
25,000 HTML checks per month. Fully automated.
Save time using our automated web checker. Let our crawler check your web pages on the W3C Validator.
The specified CSS filter is not a standard one, and may only work in some browsers.
font-display isn’t a CSS property, it’s a descriptor for use with the @font-face at-rule.
Still checking your large sites one page at a time?
Save time using our automated web checker. Let our crawler check your web pages on the W3C Validator.
This issue is a false positive by the W3C validator, fixed in the latest versions of Nu Validator.
The value revert is indeed a valid value for the CSS property font-size.
The @import CSS rule can be used to import a style sheet into another style sheet. It must appear at the top of the document, and after any @charset declaration.
The max-width CSS property sets the maximum width of an element. It prevents the used value of the width property from becoming larger than the value specified by max-width.
This property can express a value in different units like px, em, % or ch, and keyword values, but auto is not an allowed value.
Some examples of valid values for max-width:
The value specified for the min-height CSS attribute is not valid.
When was the last time you validated your whole site?
Keep your sites healthy checking for A11Y/HTML issues on an automated schedule.
Источник
Как проверить HTML валидацию сайта — основные ошибки
Разделы блога
Проверка валидности HTML кода сайта обязательно входит в мой технический аудит. Но не нужно переоценивать значимость ошибок валидации на SEO продвижение — она очень мала. По любой тематике в ТОП будут сайты с большим количеством таких ошибок и прекрасно себе живут.
НО! Отсутствие технических ошибок на сайте является фактором ранжирования, и поэтому пренебрегать такой возможностью не стоит. Лучше исправить, хуже точно не будет. Поисковики увидят ваши старания и дадут маленький плюсик в карму.
Как проверить сайт на валидность HTML кода
Проверяется валидация кода сайта с помощью онлайн сервиса W3C HTML Validator. Если есть ошибки, то сервис выдает вам список. Сейчас я разберу самые распространенные типы ошибок, которые я встречал на сайтах.
- Error: Duplicate ID min_value_62222
И за этой ошибкой такое предупреждение.
- Warning: The first occurrence of ID min_value_62222 was here
Это значит, что дублируется стилевой идентификатор ID, который по правилам валидности html должен быть уникальным. Вместо ID для повторяющихся объектов можно использовать CLASS.
Исправлять это желательно, но не очень критично. Если очень много таких ошибок, то лучше исправить.
Аналогично могут быть еще такие варианты:
- Error: Duplicate ID placeWorkTimes
- Error: Duplicate ID callbackCss-css
- Error: Duplicate ID Capa_1
Следующее очень распространенное предупреждение.
- Warning: The type attribute is unnecessary for JavaScript resources
Это очень частая ошибка при проверке валидации сайта. По правилам HTML5 атрибут type для тега script не нужен, это устаревший элемент.
Аналогично такое предупреждение для стилей:
- Warning: The type attribute for the style element is not needed and should be omitted
Исправлять эти предупреждения желательно, но не критично. При большом количестве лучше исправить.
- Warning: Consider avoiding viewport values that prevent users from resizing documents
Это предупреждение показывает, что нельзя увеличить размер страницы на мобильном или планшете. То есть пользователь захотел посмотреть поближе картинки или очень маленький текст и не может этого сделать.
Я считаю это предупреждение очень нежелательным, для пользователя неудобно, это минус к поведенческим. Устраняется удалением этих элементов — maximum-scale=1.0 и user-scalable=no.
- Error: The itemprop attribute was specified, but the element is not a property of any item
Это микроразметка, атрибут itemprop должен находиться внутри элемента с itemscope. Я считаю эту ошибку не критичной и можно оставлять как есть.
- Warning: Documents should not use about:legacy-compat, except if generated by legacy systems that can’t output the standard doctype
Строка about:legacy-compat нужна только для html-генераторов. Здесь нужно просто сделать но ошибка совсем не критичная.
- Error: Stray end tag source
Если посмотреть в коде самого сайта и найти этот элемент, видно, что одиночный тег прописан как парный — это не верно.
Соответственно, нужно убрать из кода закрывающий тег . Аналогично этой ошибке могут встречаться теги . Эту ошибку нужно исправлять.
- Error: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images
Все картинки должны иметь атрибут alt, я считаю эту ошибку критичной, ее нужно исправлять.
- Error: Element ol not allowed as child of element ul in this context. (Suppressing further errors from this subtree.)
Здесь не верно прописана вложенность тегов. В
- должны быть только
. В данном примере эти элементы вообще не нужны.
Аналогично могут быть еще такие ошибки:
- Element h2 not allowed as child of element ul in this context.
- Element a not allowed as child of element ul in this context.
- Element noindex not allowed as child of element li in this context.
- Element div not allowed as child of element ul in this context.
Это все нужно исправлять.
- Error: Attribute http-equiv not allowed on element meta at this point
Атрибут http-equiv не предназначен для элемента meta, нужно убрать его или заменить.
- Error: Attribute n2-lightbox not allowed on element a at this point.
- Error: Attribute asyncsrc not allowed on element script at this point.
- Error: Attribute price not allowed on element option at this point.
- Error: Attribute hashstring not allowed on element span at this point.
Здесь также нужно или убрать атрибуты n2-lightbox, asyncsrc, price, hashstring или заменить их на другие варианты.
- Error: Bad start tag in img in head
- Error: Bad start tag in div in head
Тегов img и div не должно быть в . Эту ошибку нужно исправлять.
- Error: CSS: Parse Error
В данном случае здесь не должно быть точки с запятой после скобки в стилях.
Ну такая ошибка, мелочь, но не приятно) Смотрите сами, нужно убирать это или нет, на продвижение сайта никакой совершенно роли не окажет.
- Warning: The charset attribute on the script element is obsolete
В скриптах уже не нужно прописывать кодировку, это устаревший элемент. Предупреждение не критичное, на ваше усмотрение.
- Error: Element script must not have attribute charset unless attribute src is also specified
В этой ошибке нужно убрать из скрипта атрибут charset=»uft-8″, так как он показывает кодировку вне скрипта. Я считаю, эту ошибку нужно исправлять.
- Warning: Empty heading
Здесь пустой заголовок h1. Нужно удалить теги
- Error: End tag br
Тег br одиночный, а сделан как будто закрывающий парный. Нужно убрать / из тега.
- Error: Named character reference was not terminated by a semicolon. (Or & should have been escaped as &.)
Это спецсимволы HTML, правильно нужно писать © или ©. Лучше эту ошибку исправить.
- Fatal Error: Cannot recover after last error. Any further errors will be ignored
Это серьезная ошибка:
После ничего вообще не должно быть, так как это последний закрывающий тег страницы. Нужно удалять все, что после него или переносить выше.
- Error: CSS: right: only 0 can be a unit. You must put a unit after your number
Нужно значение в px написать:
Вот аналогичная ошибка:
- Error: CSS: margin-top: only 0 can be a unit. You must put a unit after your number
- Error: Unclosed element a
— это парный тег, а здесь он не закрыт, соответственно, нужно закрыть. Ошибку исправлять.
- Error: Start tag a seen but an element of the same type was already open
- Error: End tag a violates nesting rules
Здесь отсутствие закрывающего тега нарушает правила вложенности, откуда идет уже фатальная ошибка.
- Fatal Error: Cannot recover after last error. Any further errors will be ignored
Это частный случай, так конечно нужно смотреть индивидуально.
- Warning: The bdi element is not supported in all browsers. Please be sure to test, and consider using a polyfill
Элемент bdi не поддерживается во всех браузерах, лучше использовать стили CSS, если нужно изменить направления вывода текста. Это не критичное предупреждение.
- Error: A document must not include both a meta element with an http-equiv attribute whose value is content-type, and a meta element with a charset attribute
Здесь 2 раза указана кодировка:
Нужно убрать в начале. Ошибку лучше исправить.
- Error: Bad value callto:+7 (473) 263-22-06 for attribute href on element a: Illegal character in scheme data: space is not allowed
Здесь запрещены пробелы для атрибута href, нужно писать так — callto:74732632206. Ошибку лучше исправить, но не критично.
- Error: CSS: max-width: Too many values or values are not recognized
И аналогичная ошибка:
- Error: CSS: max-height: Too many values or values are not recognized
В данных случаях для max-width: и max-height: не поддерживается свойство auto. Должно быть конкретное значение в px, % и других единицах измерения для CSS. В целом, эти ошибки не критичные.
- Error: The for attribute of the label element must refer to a non-hidden form control
Атрибут label должен относиться к фрагменту id с идентификатором «control-label». То есть нужно в код формы вставить кусок Тоже ошибка не критичная.
- Error: Legacy encoding windows-1251 used. Documents must use UTF-8
Кодировка windows-1251 уже устарела, сейчас везде используется utf-8. По хорошему нужно делать сайт изначально на utf-8, иначе он или отдельные страницы могут отображаться кракозябрами. Но это не критичная ошибка. Если у вас с сайтом все ок, то можно оставить, как есть.
Вот еще похожая ошибка:
- Error: Bad value text/html; charset=windows-1251 for attribute content on element meta: charset= must be followed by utf-8
Для атрибута content кодировка должна быть utf-8. Смотрите сами, хотите исправлять это или нет, не критично.
Заключение
После того, как сделана полная проверка, я составляю файл с грубыми ошибками и передаю его моим программистам или технической поддержке клиента. Кстати, почитайте интересную историю, как я искал себе программиста.
Итак, теперь вы знаете, как проверить валидацию сайта с помощью онлайн сервиса W3C HTML Validator, но как я сказал валидность кода далеко не самый важный фактор ранжирования, скорее всего после исправления ошибок вы не заметите существенной разницы в позициях или трафике сайта. Но я считаю, что все равно нужно привести сайт в порядок, и надеюсь, моя статья вам в этом помогла.
Сергей Моховиков
Здравствуйте! Я специалист по продвижению сайтов в поисковых системах Яндекс и Google. Веду свой блог и канал на YouTube, где рассказываю самые эффективные технологии раскрутки сайтов, которые применяю сам в своей работе.
Источник