This patch adds a compatibility version of FileTypeResolver.

* ColorTextField, helper methods, and regex for validating and handling text input

* Refactored structure to avoid creating new component for validation

* Style to adapt to error indicator

* Tests for validating input in ColorPickerPreview component's TextField

* Merge branch 'master' into colorpicker_validation

* Fix path to server class

* Fix test: Submit the new value

* Fix test: ignore Phantom JS

* Fix hsl+hsla validation patterns to accept '%', test value tweaking

* Merge branch 'master' of github.com:vaadin/framework into colorpicker_validation

* Fix: remove warning when color is updated from elsewhere

* Revisions: input validation only once, Logging level WARN

* Revisions: unit tests for color pattern matching

* Revisions: moved parsing to utility class, tests for parsing all accepted input formats

* Fixed import in tests, comments

* Revisions: Logger as constant, ignore utility class in serialization test

* Corner case tests

* Revisions: protected method for parsing error text, fix to test

* Revisions: NPE fix

Fixes #10170

Fixes #9917

Fixes #10647
Fixes #10498

Fixes #9765

* Add missing null check to Binding

Adds the ability to set the content mode for the description of a menu item that is part of a menu bar.
This functionality was already available for every AbstractComponent but missing for the menu items of menu bars.
If no content mode is specified it defaults to the PREFORMATED content mode.

Fixes #10476

Binder.setReadonly will ignore bindings with null setter
or property without an accessible setter when changing
field read only flag.

Fixes #10252

* Changed retrieval of names of nested properties (#10159)

The getName() function in NestedBeanPropertyDefinition will return only the top level name, which causes problems when adding a nested property that has the same name as a non-nested (e.g "value" & "sub.value")

This change should fix this behaviour by changing the return value of "getName()" of NestedBeanPropertyDefinition and introducing a function "getTopLevelName()" that only returns the last part of the full name for where it's needed

This patch also adds ValueChangeEvent as a parameter to field value change method in Binder.

* Rename HierarchicalDataCommunicator#getMapper to getHierarchyMapper

* Make rpc field in Notification private

* Change DropIndexCalculator.ALWAYS_DROP_TO_END to a generic static method

* Move EditorImpl#editRow documentation to the interface level

* Correct GridDragEndEvent, GridDragStartEvent constructor javadocs

* Revert SharedState.registeredEventListeners to a Set

* Rename GridDropTarget dropAllowedOnSortedGridRows

* Rename ColumnState.contentMode to tooltipContentMode

This commit extracts the private nested class AbstractBeanPropertyDefinition from BeanPropertySet to a public class of package com.vaadin.data.

Additionally, the nested protected class PropertyFilterDefinition is extracted from NestedBeanPropertyDefinition to a public class in package com.vaadin.data.

The old name GridDragger gave an impression that you're dragging the whole grid instead of rows.

This pathc also switches GridDragger to by default not allow drops on rows when the
grid has been sorted.

* Added Griddragger.

* Refactored the GridDragger to match FW style

Unit tests, Test UI and documentation to come next.

* Change DropMode to BETWEEN and add Test UIs

* Simplify GridDragger API

* Fixes and unit tests for GridDragger

Fixed issues regarding drop index calculation when sourche and target grid is the same.
When the ListDataProvider is not internally using List, always drops to the end.
Updates the old data provider instead of creating a new one to preserve filters&sorting.

* Add new drop mode ON_GRID for GridDropTarget

Also adds a way to not accept drops on rows when the user has sorted the grid.
This way the bad UX can be avoided for showing the drop indicator for the wrong place when the grid has been sorted.
This has not been made default behavior to GridDropTarget since it would change behavior compared to 8.1.
Instead if is triggerable via API in GridDropTarget.

* Refactor sorted grid drop logic to server side

* Block setDropMode calls

Blocking setDropMode set values if the grid has been sorted and drop on
sorted rows is not allowed. The value is used once the grid is not sorted
anymore or the drops are allowed on sorted rows.

Fixes #10195

Fixes #9210

* HasItems.setItems(T... items) should allow edits

Arrays.asList() creates a immutable Arrays.ArrayList, preventing users from doing dataProvider.getItems() and updating the returned collection. This makes it impossible to keep the same data provider, update it and keep the filters & sorting, and then just call dataProvider.refreshAll() to get changes visible. We should not require users to create a new data provider in this case.
This is the same for DataProvider.ofItems(T... items)

* fix missing whitespace from test error message

* add Grid#Column#get/setAssistiveCaption

* fix test and update doc

* move testGridAssistiveCaption to GridTest

* delete test file

* delete test file

* Delete GridAssistiveCaptionTest.java

* Create GridAssistiveCaptionTest

* Create GridAssistiveCaption

* Rename GridAssistiveCaption to GridAssistiveCaption.java

* Rename GridAssistiveCaptionTest to GridAssistiveCaptionTest.java

* Reformat using eclipse

Also improve naming by replacing one-letter variable names.

Also use "event" as the name for events

* Variable names to conform to naming convention.

* Use static constants where it makes sense

* Grid column to be sortable when implemented/supported
* Fix GridDeclarativeTest
* Parameterize to Grid<Person>
* Revert Parameterize to Grid<Person>, JDK with generics.
* Assertions for other columns
* Fix test

Fixes #8792

* Grid.removeColumn() not to fail silently (Fixes #8056)

* Compilation with JDK

* Fix removeColumnByColumn_alreadyRemoved test

* Use ExpectedException