canvas-datagrid

Forgot default value and a code path for issue #89. Should have tested more thoroughly. Really, should have written a test for the feature. I am only human.

This release fixes a scroll accuracy and performance issue introduced in v0.19.1.

Warning! Major breaking change!

This change can be very negative for large record sets if you don't set the grid dimensions! You need to be sure you've set the height and width of the grid component if you're upgrading from v0.18.x to > v0.19.x. No longer is the component implicitly set to 100%, it can now implicitly grow to hundreds of thousands of pixels in height based on the data therein causing a major slowdown (the browser will appear to freeze).

In order to allow the grid to behave more like a standard DOM element height and width are now set to auto. Meaning it will grow with the data, shoving other elements in the DOM around like a table tag.

Prior to this version the height and width of the grid canvas was set to 100% of the container of the grid. This caused the grid to be constrained to the height and width of the parent element. This is no longer the case. The grid is now by default set to be the height and width of the data; the actual size of the rows and columns in pixels.

To retain the same behavior as versions prior to v0.19.0 set the height and width of the grid element to 100% (this is what it was implicitly before). Scroll bars will appear on the canvas when the data inside the canvas exceeds the size specified in the height/width.

Impact for for browsers that are not compatible with custom tags or web components:

The same applies for non webcomponent browsers. A major change here is that there is no longer a section tag surrounding the canvas element. Now it is just a canvas element. You can supply your own canvas element, setting the parentNode argument to a canvas element does this, if you set parentNode to a non canvas element (that can take a child) a canvas will be created an added to it.

Mixup in the order in which npm was published means 0.18.27 was published as 0.18.28, requires a resync. Apologies.

fixed bug where storage data that did not have column visibility state would crash grid

Fixed issue #63. Fixed rare bug where mouse would move over grid even when it is invisible. Don't ask me how, it just does and it needed to be accounted for.

Fixed two blocking issues #68, #69. Fixed context menu re-re-placement bug.

Reverting the changes made in the last release related to high DPI displays.

Small experimental bug fix to fix issue with high DPI displays. This might actually break support for high DPI displays.