# Abaco HTML 4.0 Test Pages: Explanations

**index.html**  
This is the entry page for the whole A/B test set. It links to all twelve feature pages and also shows the expected before/after behaviour in one table, so you can run the unpatched browser first, then the patched one, and compare the same pages in the same order.

**01-hr.html**  
This page tests whether Abaco uses `<hr>` attributes like `width`, `align`, and `noshade`. Before the patch, the rules tend to look mostly the same; after the patch, different widths should be visible, centered and right-aligned rules should move accordingly, and `noshade` rules should look flatter than the default etched ones.

**02-imgsize.html**  
This page tests image placeholder sizing when the image cannot be loaded but HTML `width` and `height` are present. Before the patch, the placeholder may ignore the specified geometry and surrounding text or table layout can shift; after the patch, space should be reserved using the declared size, including border and spacing, so the layout stays stable.

**03-select.html**  
This page tests whether `<select>` respects the `selected` option instead of always showing the first item. Before the patch, the dropdowns tend to start with the first option; after the patch, `Blue` and `Large` should appear initially, while the list without `selected` should still default to the first option.

**04-forms.html**  
This page tests two form details: `maxlength` and percent-encoding of field names in the query string. Before the patch, text fields may accept more characters than allowed and special field names may appear raw in the URL; after the patch, input should stop at the declared maximum and names like `user&name` or `my field` should be encoded properly on submit.

**05-fragments.html**  
This page tests local `#fragment` navigation inside the same document, including one anchor placed inside a table. Before the patch, clicking fragment links may not scroll locally in a reliable way; after the patch, Abaco should jump in place to Section 1, Section 2, the table anchor, and the bottom anchor without treating them like ordinary external navigation.

**06-title.html**  
This page tests whether a link’s `title` attribute is shown in the button 2 status text. Before the patch, middle-click status usually shows only the URL; after the patch, titled links should show URL plus title, while links without a title should still show only the URL.

**07-lists.html**  
This page tests hanging indent for list markers in unordered, ordered, and nested lists. Before the patch, bullets or numbers may sit too much like ordinary body text; after the patch, the marker should hang to the left and wrapped lines should align with the item text rather than with the bullet or number.

**08-tables.html**  
This page tests row background colours and cell vertical alignment. Before the patch, row colours may be ignored and cells may all look top-aligned; after the patch, coloured rows should appear, top/middle/bottom alignment should be visible in the tall cells, and the row fill should not paint over the outer table border.

**09-captions.html**  
This page tests table captions, both on top and on the bottom, including a long caption that has to wrap. Before the patch, captions may not be drawn at all; after the patch, they should appear in the correct place and the long caption should lay out cleanly above the narrow table.

**10-imagemap.html**  
This page tests client-side image maps using three shapes: rectangle, circle, and polygon. Before the patch, the map areas are not honoured as separate clickable zones; after the patch, clicking the red, green, and blue regions should send you to three different target pages.

**11-frames.html**  
This page tests frame borders and frame margins in a simple two-column frameset. Before the patch, the frame contents may appear packed edge-to-edge; after the patch, visible borders and different inner margins should make the left and right frames look more clearly separated.

**12-refresh.html**  
This page tests meta refresh handling. Before the patch, nothing should happen and the page will just sit there; after the patch, it should navigate to `01-hr.html` after about five seconds on the next mouse click or key press.