Dev: PHP output support for markdown, as it is used on the site in a few
places
Merge branch 'master' of github.com:DataTables/DataTablesSrc
Fix: Destroy error if the table has been destored completely by the user
before calling destory() (i.e. overwriting with HTML)
New: CommonJS support

- This fixes DataTables/DataTables #299
Dev: Markdown updates

- In a fenced code block, need to encode the HTML elements. However, the
  HTML was being detected and saved first. Run the fencer first.

- Type links updated
Merge branch 'master' of github.com:DataTables/DataTablesSrc
Fix: Plug-in ordering didn't work on initial order

- The resolution of unknown sorting types was being done after the
  sorting structure array of objects was being calculated. As such, a
  string sort was always being done in the first instance!

- This fixes thread 20433
Dev fix: JSHint error from last commit
Fix: jQUery object will fail as a column selector

- This fixes #2
Fix: Column sorting classes might not be applied correctly

- If you use multiple column definations such that a columns' sorting
  options are initially disabled and then enabled, the sorting classes
  for the header were not being applied correctly.

- The fix is to always assign classes based on the most up-to-date
  information for the column.

- This fixes DataTables/DataTables #303
Updated: SQL exported compatible for MySQL, Postgres, SQLite and
SQLServer
Dev: Renaming demo database table for naming consistency
Fix: Ajax data wasn't being sent for non-server-side processing

- If you used client-side processing ajax, the parameter passed into
  _fnBuildAjax is an array, needed for the old 1.9 compatiblity, but the
  ajax wasn't transforming this into a data object and then sending it
  to the server. The fix is to check if the data passed in is an array
  or not - if so, transform it to an object
Fix: `grid` ARIA role should be on the `table`, not the container

- Feedback from James Craig - author of WAI-ARIA specification.
Fix: Keyboard navigation of the paging control

- Because DataTables is destroying and creating elements for the paging
  control, focus is lost when navigating via keyboard. This is a real
  pain when trying to operate DataTables that way! Fix is to refocus on
  the new element.
Fix: Don't redraw the table for page change when no change needed

- If you were to click the 'previous' button when on the first page, the
  table would redraw - that's the easiest manifestation of this bug to
  see. There is no need to redraw the table when the paging hasn't
  changed, so don't.

- This fixes DataTables/DataTables #304
Fix: Legacy API fnGetData with no parameters was flattening the return
array
Fix: Accessibility improvements

- Remove the aria-relevant from the info text to use the default,
  otherwise it was reading information that isn't very useful
- Change info text role to `status`
- Remove `role=row` from header - this is experimental and might change.
  Might need it on this row and all rows in the table
- Based on feedback from James Craig (thanks!)
Fix: Selector couldn't be given as an API instance with indexes

- It is useful to be able to filter row indexes by a condition and then
  operate on the resulting array of indexes, but before the selector
  would only itterate over real arrays. So if you passed is an API
  instance with the result set being the indexes to delete, it wouldn't
  work!

- Fix is to loop over anything which has a `length` property

- Thread 20572
Fix: Accessiblity - Add `role=row` attribute to table rows

- Feedback from James Craig on improving the accessiblity of DataTables.
  Since the `role=grid` option is added to the DataTables table, we
  should also add `role=row` to the rows in the table so the browsers
  can see them correctly. As James notes, it is debatable if this is
  needed or not but it is required in current Chrome and Webkit.

- Webkit do now allow roles to be optional in the nighties - see:
  https://bugs.webkit.org/show_bug.cgi?id=131819 . Once Apple deploy
  this in a Safari update, and Chrome also deploy support, I think this
  should be removed from DataTables core, since it will no longer be
  needed in the latest browsers, and manipulating the DOM can hit
  performance a bit.