* Moved docs comment to own row
Anyone can read the TODO comment on https://vaadin.com/docs/-/part/framework/advanced/advanced-logging.html. The comment is directly on same row as normal text, which means that it will be printed out when asciidoc is transformed to html. I moved it now to a new row which will make the asciidoc parser treat is as a comment. Please make a proper fix for it.
Make getValueProvider return ValueProvider (#8983)
* Make getValueProvider return ValueProvider
The instance can only be a ValueProvider, but the getter previously
returned a less specific type. Making the getter return ValueProvider
makes it easier to reuse the provider in other contexts that require
ValueProvider, e.g. when adding filters to a ListDataProvider.
Use computed style for Escalator size calculations (#8861)
* Use computed style for Escalator size calculations
The old method of using getBoundingClientRect does not work as expected
if a transform has been applied to the element or one of its parents.
For instance PopupView animates itself using a scale(0) -> scale(1)
animation. When scale(0) is active, getBoundingClientRect will return 0
for all sizes while computed style ignores the transform and returns the
expected value.
Fixes #8793
* Fix infinite loop in data communication
* Switch to less aggressive reset when data communication is out of sync
* Remove triggering of reset if reset is already being performed
* Avoid redundant collection of streams in DataCommunicator
Use textContent instead of innerText in TextRenderer (#8936)
* Use textContent instead of innerText in TextRenderer
This improves standards compliance and reduces unnecessary layouting.
Optimization suggested by Oskar Hýbl, Cleverbee solutions
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