| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
- Config::General compatibility patches
- copyright notice update
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
(courtesy of Antonio Cavedoni)
- sample server config to serve atom feed through W3C xslt service
- adding link rel="alternate" for the newsfeed in both whatsnew and index.html
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* send number of errors as scalar, not human-readable string
* count warnings
* preparse warnings handled by soap_warnings.tmpl (based on warnings.tmpl)
* output preparse and parse warning messages
|
|
|
|
|
| |
* send same number of errors to UI and HTTP header X-W3C-Validator-Errors
* send information on preparse warnings to soap output (not just HTML)
|
|
|
|
|
|
| |
- images already have a very long max-age
- adding a default reasonable max-age for interfaces and docs (in sample httpd.conf)
- check and feedback page, handled by the template+cgi, will issue a Cache-Control: no cache (in header.tmpl)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
fixing the "no character encoding found"
warning when validating via direct input
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1833
|
|
|
|
| |
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1809 -- porting from 0.7 branch
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
museum.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
perltidy at some point...
|
| |
|
| |
|
| |
|
|
|
|
| |
I should have committed this yesterday :(
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
and cases where nothing is set at all (also for upload, direct input).
Creating a different fatal error message for the latter cases.
|
| |
|
|
|
|
| |
invalid markup...
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
other messages),
and adding info on outcome (pass/fail) at very top of results page.
See also:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1810
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1816
|
|
|
|
| |
See http://www.w3.org/Bugs/Public/show_bug.cgi?id=1815
|
|
|
|
| |
see also http://www.w3.org/Bugs/Public/show_bug.cgi?id=1819
|
| |
|
| |
|
|
|
|
| |
http://lists.w3.org/Archives/Public/www-validator/2005Jul/0059
|
| |
|
| |
|
|
|
|
| |
note in this context (unsupported URI schemes) would be somewhat misleading.
|
| |
|
| |
|
| |
|
|
|
|
| |
providing the content where the jumpbar links point at in fatal errors anyway.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
http://lists.w3.org/Archives/Public/www-validator/2005Jul/0074.html
|
| |
|