Use setCaption Javadocs inherited from Component (#9066)
Component.setCaption has thorough Javadocs that are shadowed by a very
brief snippet in AbstractComponent and an erroneous description in
Panel. By removing those snippets, component classes will instead
inherit a much more useful description of the method.
Add server-side expand and collapse to TreeGrid (#9021)
* Add server-side expand and collapse to TreeGrid
* Add javadocs
* Fix variable naming in TreeGridHugeTreeTest
* Fix review comments
* Merge remote-tracking branch 'github/master' into 8759-server-expand
* Clear pending expands when all data is dropped
* Add documentation
* 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