Search results
Results from the WOW.Com Content Network
Adding the mw-collapsible class to a table automatically positions the toggle, and selects which parts to collapse. A common use is to make a collapsible layout table, which always displays an introduction or summary, but hides the rest of the content from immediate view.
Classes can also be used to collapse tables, so they are hidden by default. Use the class mw-collapsible to enable collapsing behaviour. Collapsible tables can be sortable, too, by also including the sortable class (see § Sortable tables). By default, a collapsible table begins expanded. To change this, add the additional class mw-collapsed.
hide, collapse, collapsed, or mw-collapsed: Uses the mw-collapsible collapsed classes to make the table collapsed with a [show] link to reveal the table. auto or autocollapse: Uses the mw-collapsible autocollapse classes to make the table collapsible, but only collapse it if there are three or more collapsible tables on the page; inner or ...
{| |+ caption table code goes here |} To start a new table row, type a vertical bar and a hyphen on its own line: "|-". The codes for the cells in that row start on the next line. {| |+ The table's caption |-row code goes here |-next row code goes here |} Type the codes for each table cell in the next row, starting with a bar:
The content in question is currently in a table so it seems logical to use collapsible tables but in the Help for Collapse (top and bottom) it mentions it can also be used to collapse complex content that includes tables. Doesn't seem to be any clear indication which is recommended.
list is a list of the section/group/etc names (the section[N]name / group[N]name / abbr[N] parameters) given in the template's code; default indicates which, if any, is to be shown expanded by default.
AOL Promotions. You’ll no longer see paid ads, but you’ll continue to see promotions for AOL products and brands. We want to keep you in-the-know of our latest product news and information.
For example, nested tables (tables inside tables) should be separated into distinct tables when possible. Here is a more advanced example, showing some more options available for making up tables. Users can play with these settings in their own table to see what effect they have.