Breaking changes
These plugins will no longer be available from the main Handsontable instance. They will be accessible analogously to other plugins, as hot.getPlugin('search')
and hot.getPlugin('customBorders')
.
Changes
- Added the
beforeContextMenuShow
hook, triggered within the Context Menu plugin. (#4973) - Fixed problems with disappearing selection handles on mobile devices. (#4943, #4936)
- Fixed a problem, where clicking on links inside cells was not possible on mobile devices. (#4570)
- Fixed a bug, where sorting didn't work when filtering was applied (#4170)
- Fixed a problem with selecting entire columns, when multiple column header levels are declared. Mostly visible with Handsontable Pro's Nested Headers plugin. (#4951)
- Fixed a problem, where the Context Menu was too narrow for its contents. (#4933)
- Modified the look of the fill handle. (#4921)
- Fixed a bug, where pressing ENTER multiple times on a merged cell at the bottom of the table was not working properly. (#4915)
- Fixed a problem with highlighting headers, when selecting entire columns. (#4875)
- Fixed a bug, where removing the first row of a merged cell sometimes caused an error. (#3473)
- Added a Russian translation. (#4854)
- Fixed a bug with handsontable editor headers overlapped the table cells. (#4787)
- Fixed a problem, where the
afterRowMove
hook returned improper parameters. (#4444) - Fixed a bug, where the
afterCreateCol
hook returned a wrongamount
parameter. (#4210) - Fixed problems with alignment and the undo/redo functionality. (#3319)
- Fixed a problem, where selecting and entire merged cell with non-contiguous selections did not highlight that merged cell. (#4860)
- Fixed a problem with the jsfiddle link in the issue templates. (#4983)
- Updated the pull request templates. (#4957)
- Added helpers for
console.log
,console.warn
etc due to IE compatibility. (#4924) - Fixed a problem, where scrolling the table on Chrome on a retina display created empty spaces. (#4498)
The corresponding Handsontable Pro version is 2.0.0
For more information on why we've went straight to 2.0.0
, check our latest blog post.