b5d28d7d30
Added test case to test flexibility. Updated old test case 443678, which is better with this fix. This fixes #523 and tries to be as general as possible. Right now the fix is only applied if the prev or next tag is a body level div, but perhaps should be applied for anything that's acting as block level element. In any case, the specific bug is killed. |
||
|---|---|---|
| .. | ||
| README.txt | ||
| case-119a.conf | ||
| case-119a@1.html | ||
| case-119b.conf | ||
| case-119b@2.html | ||
| case-119c.conf | ||
| case-119c@1.html | ||
| case-119d.conf | ||
| case-119d@2.html | ||
| case-119e.conf | ||
| case-119e@1.html | ||
| case-119f.conf | ||
| case-119f@0.html | ||
| case-352.conf | ||
| case-352@1.html | ||
| case-365.conf | ||
| case-365@0.html | ||
| case-378a.conf | ||
| case-378a@1.html | ||
| case-378b.conf | ||
| case-378b@0.html | ||
| case-412@1.html | ||
| case-434.conf | ||
| case-434@1.html | ||
| case-464a.conf | ||
| case-464a@1.html | ||
| case-464b.conf | ||
| case-464b@1.html | ||
| case-476a.conf | ||
| case-476a@1.html | ||
| case-476b.conf | ||
| case-476b@1.html | ||
| case-483.conf | ||
| case-483@1.html | ||
| case-523.conf | ||
| case-523@1.html | ||
| case-525.conf | ||
| case-525@1.html | ||
| case-611a.conf | ||
| case-611a@1.html | ||
| case-611b.conf | ||
| case-611b@0.html | ||
| case-611c.conf | ||
| case-611c@1.html | ||
| case-629.conf | ||
| case-629@1.html | ||
| case-692@1.html | ||
| case-729a.conf | ||
| case-729a@2.html | ||
| case-729b.conf | ||
| case-729b@1.html | ||
| case-836.conf | ||
| case-836@0.html | ||
| case-839@1.html | ||
| case-938.conf | ||
| case-938@0.html | ||
| case-946.conf | ||
| case-946@1.html | ||
| config_default.conf | ||
README.txt
About this test suite:
======================
These test files represent that standard regression testing that must be
performed prior to committing changes to Tidy's code. In some circumstances
results are platform specific and these notices will be displayed in the
testing results.
This test set is intended to collect tests that have been added since
the migration of HTML Tidy from Sourceforge, and the base names should
be the issue/PR number associated with the test. Multiple tests for the
same issue should be a, b, c, etc., e.g., 119a, 119b, and so on.
Some of the test cases for big fixes _may_ be in the “legacy” test set,
but we’re not going to dig into the commit history to find out. In
general, new tests should go into this directory.