Fixes #11993

* #11614: Added test which demonstrates that the fix is incomplete

* #11614: UI.doRefresh() only calls navigator when the navigation state actually changes

* Added javadoc to Navigator.getCurrentNavigationState()

* Minor: Removed accidental star imports

* Fix regression that broke PreserveOnRefresh functionality with Navigator

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

Old patch https://github.com/vaadin/framework/issues/11416 calls navigateTo allways when Navigator is present, which is wrong, since it is needed only when navigation state has truly changed.

* Add test to the fix

Navigation needs to be done also in doRefresh(..) in similar fashion as in doInit(..)

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

* Suppress unavoidable UIDetachedException

Fixes #11144

Also includes minor other javadoc and formatting fixes.

* Navigator now by default uses pushState and normal URLs

* added documentation for pushState and updated Navigator documentation

* improving docs etc, adding one TODO to be solved before merging

* pushState/replaceState no work better with changing titles

* Making uri fragment navigator work when not using specially mapped UI

* Revert to older default, add annotation for selecting

* Fix tests, add null checks

* Reorder if-clause, fix tests

* Revert unnecessary test change

* Use correct variable in UI, fix test clean up

* Updates to JavaDocs, fix some methods and tests

* Add comments, fix test ui, TODO for fallbacks

* Navigation documentation, JavaDocs, removed TODOs

* Documentation fixes

* Improve JavaDocs

* Fix link name in documentation

* Improve throws declaration in getLocation

* Change documentation about the PushState based navigation

* Add since tags

* Add since tags for UI

And remove unused imports.

Fixes #9404

* Refactor Html5 DnD client side based on API review

- Moved classes to "correct" packages.
- Removed method DragSourceExtension.clearDataTransferText()
- Remove ButtonDragSource in favor of more generic API

First step of mobile DND support.

- Add mobile html5 dnd support using polyfill
- Adds a switch for enabling mobile html5 dnd support
- Adds polyfill only when needed
- Ignore native Android Chrome drag start because doesn't work properly
(no dragend event fired)
- Add documentation on enabling mobile HTML5 DnD support
- Add mention of drag-drop-polyfill license
- Fixed issue in polyfill when not using "snapback"
- Add mention of forked polyfill

Fixes #9174

* Update since tags for 8.1.0.alpha2

* Remove API for setting arbitrary drag data
* Store the drag source component in the UI

Fixes #8893

Fix since tags for the server and shared modules and new types in client.

Running formatter:format will format all files in a submodule using an
embedded Eclipse compiler (based on Neon SR1)
according to the regular formatting settings file.

* Added support for HTML5 push/replaceState for proper deep linkin features

* Automated test script now works at least on chrome

* Uses html5 push/popstate to implement uri fragment feature

* fire legacy fragment change events also via popstate events rpc calls
* send new fragments via pushstate mechanism

* formatting

* Formatting and adding test and workaround for IE bug

* Formatting and depracated UriFragmentListener

* Aligned naming in the new API

* Ignored IE due to web driver bug

Tested a workaround with javascript based window.location.href fetch,
but that don’t seem to work stable enough.

Fixes vaadin/framework8-issues#514

Closes vaadin/framework8-issues#548

Change-Id: I4e32550e3d3095c2c914bb93d260819414d2e6e6

Change-Id: I259c659987b5b15b354e16d0be1523f4ede809f0

Change-Id: I9feaad000cb16351d281d1c0037330dfb76186ff

This patch updates server side add*Listener methods to return
a registration object and deprecates their corresponding
remove*Listener methods.

Additionally this patch removes add/removeListener methods which were
deprecated in 7.0.

Change-Id: I26ac5f11882512288fbbf601c7cb2aaff653ec76

Does not modify compatibility packages to keep to closer to Vaadin 7.7

Change-Id: Ic9c4944eb90218290545a04ecd7455eb63910012

Change-Id: I6485dee1ebba12b180a9063ed4b530f7dc63cd77

Change-Id: I4c852b7f9928e190572876690d5bef1234494a5d

Change-Id: I33f1cc33969ff74a95b1b8cc0f2add589be5aae0

The server side needs to know the client has removed the connectors to
be able to do cleanup

Change-Id: Ic3d41cc5cbab035a53bf5c99496d74858c376e73

Change-Id: I5c740f4e9cb28103bab199f9a552153d82277e7e

The comment was introuced in commit da29f74 for a constant named
CLICK_EVENT_ID, but it was accidentally left in the code when that
constant was removed.

Change-Id: I69697f517585cafb30cc223497bc8db4a919e884

Change-Id: Ie7a28488e4642a294f0341f00fc98b2ef38922b6

Change-Id: Ibf60ef8cdd21204e8ccfbb0a7d93cf88c4d8468a

An server message id counter is included in every client to server message and an
expected id is included in every server to client message. This makes it safe to
re-send any message when the client is not 100% sure the server has received the
message, without having to worry about double handling on the server side.

Change-Id: I840cc04829fc2491f35a0e6f98f07eaf46b1ea42

Change-Id: I288bae95e364277819727a99854d94fbbc98b162

Change-Id: I975eef2f06db4395925f76e40c044078028b0e66

Change-Id: Iefc27b7047836243268970605ba2e946fac55e95

Change-Id: I57cb6208613ce4fc8fce52c07ac4a18982095d2e