1
0
mirror of https://github.com/rkd77/elinks.git synced 2024-12-04 14:46:47 -05:00
elinks/test
2006-01-28 15:03:19 +01:00
..
css Add a css media test file (see bug 722). 2006-01-14 01:56:22 +01:00
docbook
ecmascript
rss
xbel
align.html
backspaces.txt
bigtextarea.html
color.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
comments.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
erreurs_en.htm Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
garbage.html
href_tests.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
imgmap.html
javascript_broken.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
libtest.sh
longtitle.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
malicious_uris.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
optgroup.html
poocs.net.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
portlink.html
README
refresh.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
subsup.html More sub/sup tests. 2005-10-19 23:05:41 +02:00
tabindex.html
tablebg.html
tables.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
target_blank.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
td-width.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
underline.html Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
xmp.html

This directory contains various weird documents for testing whether we're
parsing and rendering them properly. Frequently, documents are getting added
here when we implement feature needed for their correct presentation or fix bug
occuring inside of these documents. No automated testsuite yet, though.

Possible meaningful content of the documents is completely irrelevant and you
should ignore it. Noone takes any responsibility for it :).