v0.4.9

Another attempt to better handle NaN values across browsers and different OS, fix provided by @dulldrums

v0.4.8

Merged fix to make sure NaN values are not rendered (thx @dulldrums for fix)

v0.4.7

Fixed issue with colorscales that use color steps with transparency when using webGL rendering (thanks to @sfalmo for pull request)

v0.4.6

• Implemented better fallback support for mobile devices
• Solved issue with no transparency when using 2d context

v0.4.5

Fixed type in two colorscale names:

• yignbu changed to ylgnbu,
• yiorrd changed to ylorrd

v0.4.4

• Fixed issue where when disabling WebGL for rendering the highest value of the specified domain was not being rendered / being clipped

v0.4.3

• NaN values in data are now not rendered (no need to add NaN as noDataValue)
  Notice: The way of handling NaN in the shader is not clearly defined so different browser implementation could have different visualization results.
  I would recommend converting NaN to a know noDataValue and using that value in the configuration (such as Number.MIN_VALUE)

v0.4.2

• Added new parameter displayRange and enabler applyDisplayRange to only display a certain value range without modifying the domain
• Added method setDisplayRange that can be used to set a new range before rendering (automatically sets applyDisplayRange to true)

v0.4.1

• New turbo colorscale added

New dataset combination function

Adding possibility to combine multiple datasets using math expressions;
Mathematical expression can contain operations with integer/float values, dataset identifiers or GLSL supported functions with a single parameter.