Clean up module vs class descriptions, +@since 3.5.0 Moved the lengthy text from the module description to the class description so the module page would look cleaner. Added note for each class extension to point readers to the DataTable class for docs on the APIs contributed by this class, since they all have @for DataTable.

Add back compat for field and id column configs core.js added the back compat. The others share an update of changing references of col._yuid to col.id.

Add scope attribute to headers

Add column _id as data attribute in markup This makes it easier to tie the header clicks to the column configs for sorting, and it makes it possible for scrolling DT's to duplicate headers and relay fixed header clicks to the sort operation.

Declare first header column via class Can't rely on .yui3-datatable-header:first-child because nested headers can include a rowspan first column, which makes the first th in the next row (which is not along the left edge of the table) lose its left border. Irritatingly, webkit did not behave correctly (hide the border), so I thought it was a problem common to the other browsers. Clearly, bias was in play.

Move col._parent assignment to Core Needed for getColumn.

Remove all traces of aria. SRs read better without Sad state of affairs, but NVDA and VoiceOver read the table better when no aria roles are assigned. Ticket #2531426

+col.cellTemplate and headerTemplate support For column level control over the cell rendering, to allow implementer to render some body cells as <th>s

Underscore-prefix added column props. Fix rowClass Also update API docs for formatter object properties. The API docs described the ability for formatters to add classes to the row, but the functionality was broken by other code tweaks during dev. Code and API docs updated to restore the functionality.

Typo fix for column className config

Add support for className column config className is added to the row template, obviating the need for a column formatter just to add a class to the <td>. This is used in datatable-sort, and will likely also be used in datatable-edit (or whatever the module is called).

Add headers to nested header `<th>`s Screen readers still hate my markup for this, but we'll get it worked out soon.

Add row, columnheader, gridcell roles, +scope

Review feedback #3 (from Satyam) * typo in getRow * move caption and summary attr => _uiSet* to _UI_ATTRS * rename {classes} placeholder {className} * header cells get column class as well * header cells get yui3-datatable-header class * data cells get yui3-datatable-cell class * Core now assigns columns a _id which is name, key, or yuid w/ uniqueness counter * column class names now yui3-datatable-col-foo (added -col-) * use toJSON() to get data for the formatters * replace CSS targeting tags with classes

Remove backslash escaping in `code _snippets` Not needed in the latest yuidoc

Remove liner divs. Reduce CSS. Add skinnable:true

Move tbody,foot,head creation into Core It simplifies logic to have the Views working with the table sections rather than the table itself. Unrelated, renamed _uiUpdateWidth to _uiSetWidth to override the Widget method that just set dims on the boundingBox.

Loosen search for existing thead It was looking for an existing thead with the DT class on it, but ANY thead would need to be replaced. Options were: 1. Accept only an appropriately classed thead and replace any other thead, or 2. Accept any thead and use it rather than creating a new one. I chose the latter, but may change my mind later.

Clean up PE plumbing, +column mutation Baseline handling of columns change is to rerender the thead. Optimized handling can be relegated to a plugin. If render() finds an existing, appropriately classed thead, it will skip rendering and use that one.

Finish API docs for current API There will be more. Oh, so much more.

Add API docs and other minor code updates.

Add `getClassName` and use `container`/`modelList`

Simplify stack processing. Instead of managing two stacks, one for the row and one for the column index, just use one stack and have each entry store the row and index.

Decouple column parsing, +nested cols The parsing of column array data was in Core, but was parsed into three different forms: 1) for column access from Core's get('columns.<key>') 2) for column prep for header rendering 3) for column prep for body rendering Now the columns are passed to the views to do with as they will, and Core only does what is needed for #1. Also, parsing nested headers efficiently is a pain in the ass. The 'children' config doesn't allow implementers to choose which cells get rowspan when the number of header rows is greater than the number of column descendant levels. As is done in 3.4.1, parent cells are always rowspan 1. I prefer to have data related columns have rowspan 1, but the logic to support that with the "children" config would be crazy complex. Implementers can move stuff around in `table.head.columns` before `render()` if they want different cell placement and spanning.

+getCell and getRow. Grouped, alphabetized methods Conflicts (resolved) src/datatable/js/pe.js

+ column.formatter & column.nodeFormatter Other bug fixes. Can render from array. Column ordering works. Movin right along.

Initial drop of DataTable rearchitecture Renders a table from supplied columns and data as a ModelList with Model instances. A lot more plumbing in place, but not yet exercised. Progressive enhancement extension in src/pe.js, but doesn't have build files yet.