Hibernate Validator 5+ requires
- Validation API 2+
- explicit Expression Language dependency

Fixes #10437

* Add 1px buffer to Escalator column natural widths.

The purpose of the buffer is to avoid subpixel handling issues,
especially when zoomed in or out.

In case fractions need to be adjusted for browser compatibility, round
up to ensure the contents have the space they need.

Fixes #12048

* Fix to natural column width calculations in Table footer.

NOTE: components within row generator are not an officially supported feature and can cause issues within your application.

Fixes #11235

* Update release-note template for 8.12.0.alpha1

* Add a regression test for Table's RowGenerator feature.

There used to be a TB2 test for this once upon a time, but for some
reason that never got converted into a TB3 test before getting removed.

* Explicitly remove old dataprovider listener when new one is set

If not done, this can cause memory leakage

* Formatting

* Fixed coding style

* Take into account further scenarios

Component maybe detached permanently and thus data provider listener needs to be remove in detach. Also if this is only momentary remove from layout add back cycle, re-setup is needed in attach, in case it was not already setup before attaching by setDataProvider.

* Change super.detach() call order

* Added null check to getDataProvider

* Setting dataProviderListener to null on detach

* Removing listener only if it exists

* Fix

It is possible when Vaadin 8 is used with MPR, that ui.getCurrent().getSession() returns null.

See: https://github.com/vaadin/multiplatform-runtime/issues/5

There might be pending requests in the queue when a resync request is
made (e.g. through a theme change). This can cause conflicts if the
resync request is handled immediately. Therefore the resync request
should also be added to the queue and only get resolved when
doSendInvocationsToServer() gets triggered again.

Fixes #11954

- If the Grid has any columns with non-fixed widths, the presence of a
vertical scrollbar affects the column width calculations. Horizontal
scrollbar should only be shown when actually needed.

Fixes #12049

Delayed size changes caused by added or removed scrollbars should be
taken into account.

Calculate number of the week in the year based on Date. Note, support for "ww" is missing from GWT DateTimeFormat and java.util.Calendar is not supported in GWT, hence DIY method is needed.

Fixes: #10603

Adopted from https://github.com/vaadin/flow/pull/8567

Fixes #12029

* Add tests

* Fix getVisibleFrozenColumnCount() if SelectionMode is multi

* Update chrome version to 83

* Update screenshots

* Fix ComboBox in read-only mode allowing value change by user

Fixes #12021

* Fix popup hiding condition

Co-authored-by: Tatu Lund <tatu@vaadin.com>

* Add autocomplete prevention to DateField

Autocomplete popup will interfere DateField's own popup

* Adding disableBrowserAutocomplete(..) in WidgetUtil

* Change VComboBox to use WidgetUtil.disableBrowserAutocomplete(..)

* Change to use WidgetUtil.disableBrowserAutocomplete(..)

* Change VFilterSelect to use WidgetUtil.disableBrowserAutocomplete(..)

* Adding WidgetUtil.disableBrowserAutocomplete to VTextualDate

* Adding missing import

* Adding missing import

* Sanitize caption used in compatibility Grid header

Cherry pick of #11644

Issue #11246, slightly modified cherry-pick from #11247

* Fix scrolling problem in table in Chrome 56+

Issue #8707, slightly modified cherry-pick of #10492

Added a toggle in Table (and thus TreeTable) where you can explicitly
disable multiselect touch screen detection. This allows you to work
around issues on hybrid devices that have both a touch screen and a
keyboard where you don't want automatic simple multiselection applied.

Fixes #11601, slightly modified cherry-pick of #11641

Adapted from V7 fix #10999

Fixes #11993

IllegalStateException may occur if user has scrolled Grid (compatibility library version) so that Escalator has updated, and row under Editor is no longer there

Chrerry pick from https://github.com/vaadin/framework/pull/11467

* Removing deprecated parameter

Fixes: https://github.com/vaadin/framework/issues/11958

Issue #11893, cherry-pick from #11984

Fixes #10914

Fixes #10844

Fixes #11958

Fixes #10580

In Firefox and IE11, the 'Create Link' button of the RichTextArea (RTA) only works by turning some highlighted text into a link (by adding the inserted URI as the href property of the text). In that, the RTA in these two browsers behave similarly to the way it does in Chrome and Edge. However, in Firefox and IE11, clicking the 'Create Link' button has no effect if no text is pre-selected by the user. This is different from the button's behavior in Chrome and Edge where the user's provided URI is inserted, both, as the displayed text and its href property if no text is highlighted.

This fix enables the RTA's 'Create Link' button to work consistently across the supported browsers. Specifically, (and in addition to enabling adding the href property of a highlighted text), this fix enables Firefox and IE11 to also insert a new Uri as a text and its href property if no text is already highlighted.

fixes #11888

* Take overlays into account in getConnectorForElement.

Fixes #11212

Fixes #11824

Fixes #11973

The previous patch https://github.com/vaadin/framework/pull/11951 did fix the problem (frozen column indicator wrongly positioned)  it was meant to, but caused a regression in hiding / un-hiding. 

This new fix addresses both problems, i.e. it applies multiselect column compensation in other way, without causing problem in hiding / un-hiding logic

Fixes https://github.com/vaadin/framework/issues/11970

* Don't center a window that has already been removed.

Fixes #11942

* Updating release notes

* Fixing typo