v0.1.0-alpha.14

One DataTable fix. Nothing renders differently.

Fixed

A control inside a clickable row no longer also activates the row (#24). A row with onRowClick containing an Edit button had two actions competing for one click, and both fired: the button edited and the row also navigated away from the thing just edited. The same held for a nested link, input, select, or anything else focusable, and on Enter as well as on click.

The row is now the fallback, so anything more specific inside it wins. Every consumer had this and none could fix it from outside, since the handlers are the component's own.

Found while a consumer migrated off its vendored copy, whose test suite covered the case.

Before you upgrade

A patch. Nothing visual changes; a secondary action simply stops triggering the row's primary one, which is what placing that control there already implied.

Full changelog: v0.1.0-alpha.13...v0.1.0-alpha.14