Fixed touch scrolling issue in Surface and WP devices (#18737)
Fixed by using pointerevents instead of touchevents when the browser is IE11,
or Edge. Also added touch-action: none; css rules into escalator.css to prevent
default touch behaviour on IE11 and Edge. Does not affect IE8 to IE10 browsers,
behaviour on those will stay the same as before the fix.
No new unit tests since we do not have automatic touch testing possibilities yet.
Please test manually with Surface: IE11 and Edge, use for example uitest:
com.vaadin.tests.components.grid.basics.GridBasicsomponents.grid.basics.GridBasics
Change-Id: Iddbf1852e6ffafc855f749d6f4ebb235ed0f5703
Moves FocusDelegate to AbstractFieldState.
This change is done to revert backwards compatibiity breaking API
change in 7.7.4 when CustomFieldState was introduced.
Change-Id: I76212a8700463140520d5482b740fe0edbfb082c
Fixed drag and drop failure when message dragged from email client (#20451)
When dragging message form email client on Windows, item.webkitGetAsEntry()
might return null creating NPE on the client side. Added additional checks
for this situation.
Change-Id: I569f7e6d0d7b137f24be53d1fbce384695ae8c73
Make clicking outside a ComboBox add a pending new item (#18366)
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
Revert "Fixed touch scrolling issue in Surface and WP devices (#18737)"
The patch prevents Escalator and Grid from ever being rendered on IE8 because element.addEventListener does not exist there
This reverts commit eb2f5ac3a7.
Change-Id: I58f6db7432a1cd10299891b2d8c55c855e87265f
Fixed touch scrolling issue in Surface and WP devices (#18737)
Fixed by using mouse events instead of touchevents when the browser is
IE or Edge (added isIEOrEdge utility method in the BrowserInfo). Also
added touch-action: none; css rules into escalator.css to prevent
default touch behaviour on IE and Edge
No new unit tests since we do not have automatic touch testing
possibilities yet.
Please test manually with Surface: IE and Edge, use for example uitest:
com.vaadin.tests.components.grid.basics.GridBasics
Change-Id: I5b37f1648e2051ea0ab4d56ab767186b532da07c
Show a sensible message for missing extensions (#10799)
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
Add valo-menu-hover stylename to make responsive menu appear w/o adding code (#19019)
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
Add tests for widgetset compilation in different modes
* 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
Johannes Dahlström
Pekka Hyvönen
Artur Signell
Johannes Tuikkala
Patrik Lindström
Henri Sara
adam
Denis Anisimov
Steven Spungin
Teemu Suo-Anttila
Marc Englund
Sebastian Nyholm