Home
Home Page
Optimization of a code: top 5
Validator - necessity of use and practical advice{councils}.
Bug in the table
Where to take validator?
5 myths Web of programming
AJAX FAQ for Java-developers
Whether really it is necessary to study JavaScript?
- XML, plain text, JavaScript or HTML - it is necessary to use what type of returned value?
Whether exist in AJAX problems with convenience of use (so we shall translate further the term usabi
How to debug JavaScript?
Whether there are problems with safety at use AJAX?
How to organize in a separate stream periodic pollings through AJAX?
JavaScript the script processing the XML-document
Style tables XSL
Rules XSL
With reference and in rules special elements also can be used
Scripts
XML from Java-classes
Lacks of start of own realization
Links
topic

Where to take validator?


Validator in the form of web - page it is offered on http://validator.w3.org. He is based on SP Clark.


Is as well validator on http://htmlhelp.com/. He too is based on SP, though and little bit changed. By authors it is declared, that he is more strict in a rating and declares potentially dangerous, though and allowable places (we shall say, open teg with unessential closing). Offer source codes validatora


Accessible podo all platforms free-of-charge validator can be downloaded from site Dzh. Clark (http://www.jclark.com/sp/). Together with parserom/validatorom in delivery it is applied potokovyj normalizator.


W3C Distributes source codes validatora on http://validator.w3.org/, but it, actually, not validator. It only adaptation klarkovskogo validatora to the web - interface, executed on a pearl. In the description of this adaptation it is unambiguously said, that it is necessary to have by the machine klarkovskij validator. Still links:

• http: // ugweb.cs.ualberta.ca / ~ gerald/validate/

• http://www.webtechs.com/html-val-svc/

• http://www2.imagiware.com/RxHTML/


Whether it is possible to name validatorom the tool from HomeSite - Validate Document?


Developers Allaire HomeSite declare, that that « … the checking program is issued by them under the name "validator" especially from commercial reasons … », and present{true} validator will not be issued by them.


The program going complete with HomeSite, breaks definition validatora: she finds and shows mistakes which have not been admitted{allowed}, and does not find mistakes which have been admitted{allowed}.

Example of its{her} wrong actions:

a) <img src = "/img/g1x1.gif " alt = ""> <img src = "/img/g1x1.gif ">

Reaction: there is no reaction.

Actually, here a mistake: it is not exposed ALT the second IMG.

b) <br/>

Reaction: a mistake.

Actually, this teg is possible{probable} in frameworks XHTML.


The aspiration to faultlessness - first attribute of professionalism, also no necessity to be guided on popular, however far from perfect a html-code portals. Probably, managers of similar sites, having analysed statistics of visitings, have found out, that 99 % of coming users will see all how the designer assumed... Probably, authors of a site intentionally eliminate as the visitors of users with the limited opportunities... However it is necessary to remember such concepts, as humanism and requirements of the law. With the advent of the official standard because of infringements of the specification there is a danger to get in court on accusation of inaccessibility of a site for those who cannot use a "usual" browser. Though in regions of the countries of the former CIS the legislation is enough limited in this respect, in the educated world the question is solved better. Availability gradually gets force of the law. Validator does not guarantee availability (because cannot be replacement of common sense), but helps to provide a due measure of support of all users.


Successful sites and faultless code to you, dear developers!