Keyboard

↓ ↑
move between the rows you can see
→
open a feature, then step into it
←
close a feature, or step out to the one above
Enter
go to the page in focus
Tab
the same rows, plus everything else on the page
/
search the whole report
m
open or close the navigation drawer
Esc
leave the search box, or close the drawer
?
this list

Fills a page's search text from that page alone

All 6 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.

A search finds a table page by everything a reader can see on it: its title, its description, its column headers and its cell values. A search finds an index page by its own title alone. A word that appears only in a rule below a feature therefore does not find the feature. It finds the rule, which is the page the reader wants.

These rows read a report of one class, Calendar rules. Its table is Leap year rules, described as "Gregorian leap year determination.". The columns of that table are Scenario, Year and Is leap year?. Its one row reads: A year divisible by four, 2004, Yes.

expected outcome broken scenario
ScenarioPageWordIn its search text?
The table's own titlecalendar-rules/leap-year-rules.htmlLeap year rulestrue
The table's descriptioncalendar-rules/leap-year-rules.htmlGregorian leap yeartrue
A column headercalendar-rules/leap-year-rules.htmlIs leap year?true
A cell valuecalendar-rules/leap-year-rules.html2004true
An index page's own titlecalendar-rules/index.htmlCalendar rulestrue
A word from the table below itcalendar-rules/index.html2004false