* 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

* Update expected Chrome version to 56

* Update screenshots

IE8 handles the sizings differently from other tested browsers so it
needs to be tested on 'left: auto' and not wrapper div width.

Refresh calendar body for show week numbers state change.

Fixed problem that disables opening of popup
after closing it by clicking the datefield-button.

* Fix gthe absolute layout component resize positioning tests.

Fixes #8413

* Call "destroy" instead of "destory" in JavaScriptRenders

For backwards compatibility, calls "destory" if no "destroy" exists

Fixes #8162

* Merge branch '7.7' into _js-renderer-destory

* Merge branch '7.7' into _js-renderer-destory

* Merge branch '7.7' into _js-renderer-destory

* Merge branch '7.7' into _js-renderer-destory

* Merge branch '7.7' into _js-renderer-destory

* Add method for refreshing all Grid rows

Fixes #8350

* Rename variables to indicate whether they use DOM index or Grid index

Grid indexes include hidden columns, DOM/Escalator indexes do not

* Prevent reorder of frozen columns when there are hidden columns

Fixes #8265

* Merge branch '7.7' into _grid-no-reorder-of-frozen-columns

* Merge branch '7.7' into _grid-no-reorder-of-frozen-columns

* Merge branch '7.7' into _grid-no-reorder-of-frozen-columns

* Merge branch '7.7' into _grid-no-reorder-of-frozen-columns

* Merge branch '7.7' into _grid-no-reorder-of-frozen-columns

* Merge branch '7.7' into _grid-no-reorder-of-frozen-columns

* Merge branch '7.7' into _grid-no-reorder-of-frozen-columns

Fixes #7880

Changing from relative to defined size leaves the component positioned wrong,
also changing from defined size to relative size leaves the component in the
wrong position with the wrong size.

Change makes the wrapper rerun setChildWidgetPosition() that adds/removes
necessary css definitions to/from the cssPosition String.

Fixes #8266

Fixes #7496

* Properly end HTML5 drag operations when no drop is performed

No auto test because of https://github.com/SeleniumHQ/selenium/issues/1365

Fixes #4060

* Make it possible to deselect what was selected on the server

Fixes #8221

* Reset selected icon when blurring a ComboBox

Fixes #8073

* Merge branch '7.7' into _combobox-icon-reset-selection

* Merge branch '7.7' into _combobox-icon-reset-selection

* Remove tracking of unregistered connectors

* Merge branch '7.7' into 8111-remove-unregistered-connector-tracking

* Merge branch '7.7' into 8111-remove-unregistered-connector-tracking

* Add tests that verify markAsDirty is called on old parent

* Merge branch '7.7' into 8111-remove-unregistered-connector-tracking

Fixes #7695

Fixes #8015

* Render font icon correctly on the 'more' menu item

Fixes #8125

Fixes #4995

* Fix chrome version

Fixes #8018

Fixes #8011

Change-Id: I0ae9144817db3bb730c80748d5e9190484b323e7

Change-Id: I404985ae0be1e7dc65171b610032f8649e700f50

Change-Id: I47427efc28c350382dba8c1f50fd332a3f4585e4

This could occur in when parent is a different entity than its children
in hierarchical data.

Change-Id: Icd53b5b5e5544a3680d0cd99702ab78224b2dc08

Change-Id: Ib0cc6c6835aab6d263f153362a328bcf2be7bc5c

It should not matter how you move from a field to the next. Tabbing
to the next field already previously caused the new item handler to
be invoked. This fixes the case when you click in the next field to
work the same way.

Change-Id: I3978d87cde8f05dce92edda2a4a116f4a15e0749

Change-Id: I2a89d3493e2f98ab1b9a0666d9dc075a2457e432

Change-Id: Ibef57aa4f8838f3bbc5f5c5500f3f4f7fc6eb438

Also remove ComponentMissingFromDefaultWidgetsetTest since it's
identical to UnknownComponentConnectorTest

Change-Id: I4b4b8f40c8376f4ea26b73d41191a3e7e811df01

- legacy DateField declarative format tests are fixed (day light saving
time is taken into account).
- CalendarMonthViewDndEvent UI because you are not supposed to work on
Sundays (when the test is broken).

Backported from master branch (Vaadin 8).

Change-Id: I5e62c09da579e9f6eb2a58a87253618d3f30b2e9

Change-Id: I99347ee1d0f2f13fcb8e110d2e7192590e4f9456

This is needed to be able to get the information from e.g. TestBench

Change-Id: I95ec6064f602e6a8b24e35cc59d467e9c8b31c1e

Change-Id: I1160e7a384b1816204eb7f4b0f52f83ed9e230c0

Change-Id: I6b045c3a693e88b3cba182ae9ea68cfa98c914b0

Change-Id: Ibb3b52b652d77a1bfa786417b1c92fd0a578035f

Change-Id: I3cfdac539111ff2e88c7ff81e6d6b9a579160423

Adding the optional "valo-menu-hover" style to the "valo-menu" element
will make the menu appear on hover - i.e when mousing over on desktop,
when tapping on touch devices (which also triggers hover).

Backported from master branch (vaadin 8).

Change-Id: I8344234a20aa93216b0116608d81e30e86d8b309

Change-Id: I7fe8c160405a69140cac511c744d89a62c401cca

Change-Id: I554d7b6ca60840bab3a032daa4847e7271086e27

Change-Id: I4e32550e3d3095c2c914bb93d260819414d2e6e6

Change-Id: Ic453aaf16ea1d44792db868e04faaba069aab3b7

* Using the default widget set
* Using no add-ons but a custom widget set
* Using add-ons with a defined widget set
* Using add-ons with no defined widget set
* Using directories with special characters (space)

Change-Id: I85450de359f410003bed94b120915b4736bc2d4f