Describes every page of the report in one index
All 3 scenarios hold
Every page carries a search box, and that box searches the whole report. The report writes one index beside its pages, tabletest-search-index.js at the output root, and every page loads it. Type in the box and the navigation tree gives way to the pages that match. A page matches when its title or its text holds what you typed. The match ignores case, and it can start anywhere in a word.
The browser does the matching. The rules below therefore state what the index holds, and not what a query gives back.
The index holds one entry for every page. Three kinds of page reach it: the root index, a feature index below the root, and a table page below that. Each entry names its page by the path from the output root. A reader who finds a page from anywhere in the report can therefore reach it from anywhere in the report.
These rows read a report of one class, com.example.orders.OrderTest, whose only table is items. The report root is the package orders.
| Scenario | Page title | Its path? | Its type? |
|---|---|---|---|
| The root index | orders | index.html | index |
| A class index | order-test | order-test/index.html | index |
| A table page | items | order-test/items.html | table |