Create drag start and drag end events for Grid to have access to dragged items on server side (#8950)
* Create grid drag source event to be able to access dragged items on server side (#8931)
* Create grid drag end event to have access to dragged items on server side (#8931)
* Change addListener method name so that no castig would be needed
* Fix drop listener in dnd UI test
* Fix review issues
* Fix more review issues
Make it possible to drop things on top of Grid rows (#8747)
* Create initial grid drop target classes
* Reorganize event listener attach and removal
* Add Javadocs and annotations
* Make it possible to drop things on top of Grid rows (#8400)
* Fix javadocs for indicator methods
* Add drop target indicator on dragover event as well in case the element doesn't have one yet.
* Remove additional drop target and formatting
* Create grid drop event and listener
* Create API for getting info about drop target row
* Add javadocs
* Rename server RPC method
* Fix javadocs
* Use Optional instead of null as return type
* Add addListener method for grid drop target and fix javadocs
* Fix some javascript
* Make all selected rows draggable (#8397)
* Add swich for changing selection mode
* Drag only visible selected rows when selection mode is MULTI
* Highlight that only visible selected rows are dragged
Add API support for setting server side drag data (#8915)
* Add API support for setting server side drag data
* Fix javadocs
* Add server side drag data API to ASCII doc
* Fix some javadocs and documentation details
* Use difference GUI component for Vaadin 8
With Vaadin Framework 8, Tutorial learner should use different setting and component for form development
* Better explanation
Check Trident version to detect compatibility mode (#8884)
IE11 in compatibility mode is actually not too old. It's just not recognized as IE11 if you leave the Trident version out of the equation. Checking the Trident version and using it to determine the actual IE version instead of trusting the possibly emulated MSIE version string.
* Update MemoryIT to report median render and request time
* Add TreeGrid and TreeTable performance test UIs
Addresses the collapsed cases for #8849, #8850
Always calculate Escalator max row count the same way (#8740)
* Rename getMaxEscalatorRowCapacity to describe what it does
* Always calculate Escalator max row count the same way
This changes Escalator to not take a horizontal scrollbar
into account when trying to determine "maximum visible rows". This will
add another row, compared to previous versions, when there is a horizontal
scrollbar. In reality, it would likely make sense to always add 10 more rows
to have some buffer above and below the visible area.
Fixes #8661