Notification should be closed after delay (#14689).
onEventPreview() method is deprecated and it's called now only for the
very first handler. We need it to work for any handler. So old
onEventPreview() method is explicitly called with updated logic for the
onPreviewNativeEvent().
Change-Id: I11d98ef0bbd284b74bbccb4f6ac2ab26de73f209
Notification delay is not set to 0 when the notification is clicked (#14368)
Reintroduce the delay timer which triggers the hiding of the
notification. When the notification is clicked, no timer is used, the
notification is hidden immediately.
Change-Id: I93ecc5dcc34c10092b85f4e0daf7ecacfef77f7a
The default hiding delay should be 0ms instead of 1000ms, according to
the server side class at least.
Change-Id: I064c01b2fdc9df4cbcbd74def8e494add22ee749
Fix overlay animation-in/out for VNotification and PopupView
- Notification delay now applied to browsers without CSS animation
support
- PopupView now also supports animation-in and animation-out, and also
shows the “loading” widget when the popup is opened and the server
response takes a little longer. The popupComponentWidget is also kept
in the popup during the animation-out
Change-Id: Idb26d87a8cf75cfa3e145ea670dacc1c87ce75d6
Fix multiple VOverlay animation-in/out related issues
Any running animation-in is now finished before animation-out is
triggered.
Moved windowClone variable into WindowConnector where it should be.
Change-Id: I0ee733d05558d46a08e5e46f821104ad98783118
Implement Notification animation with CSS (#13660)
Default opacity (90%), fade duration (400ms) and fade delay (1000ms) are
defined in the base theme.
“In” animations can be defined by using a dependent stylename
‘animate-in’ (prefixed with the widgets own primary stylename), e.g.
'v-Notification-animate-in'. That CSS class should then have a CSS
animation specified, and the CSS animation name should contain
'animate-in', e.g.
.v-Notification-animate-in {
animation: notification-animate-in 400ms;
}
@keyframes notification-animate-in {
...
}
“Out” animations are defined similarly, but with 'animate-out' as the
keyword.
The base theme contains mixins for declaring keyframes rules as well as
animation values, which include needed vendor prefixes.
Refactored deprecated GWT API’s to use newer API’s.
Change-Id: Iba929e8de8b6ce100852d472d65c9c9d0630c48f
Replace use of deprecated DOM.setStyleAttribute method (#13781)
This change is only a brain dead replacement of one specific method. In
some cases, there were some oddities in the surrounding code as well,
but these were left unresolved on purpose.
It should also be noted that DOM.setStyleAttribute just delegates to
element.getStyle().setProperty(), so any null references would have
caused problems already in the existing code.
Change-Id: I340122ac0767af9928076376f76e5bd2c5e19f9f
VNotification now works without ApplicationConnection again.
Dependencies needed by codeserver are now dependencies for client-compiler
Error message now takes into account that devModeRedirect is enabled by default
Change-Id: I079d162d9975f99fe7b91e14ad100459c80a5587
Changed implementations and APIs to use the non-deprecated Element class
wherever possible without breaking backwards compatibility.
* Methods defined in interfaces have not been touched.
* Return types have only been changed methods that should have no
existing third party callers (i.e. private, internal or @since 7.2)
* For methods that third party code might have overridden, the method
has been deprecated in favor of a new method that just delegates to the
old method.
* For methods that can't reasonably be overridden by third party code
(i.e. private, final, static, internal or @since 7.2), the parameter
type has been changed without retaining the old method.
Change-Id: I7da943a77b8d0d0b9185d8c70f87d676a275d24b
Use FQN instead of import for the bad Element class (#13287)
This is the first step towards eliminating usage of the class. Reasoning
about upcoming steps will be easier when it's clear which class
"Element" refers to.
Change-Id: Iea5547f789edc77c3b4ac95a5e2eb34d2717999e
Moved each component to its own package on client side
Class loaders have problems with referring to static inner classes (e.g.
state classes) when they cannot load the declaring class. To deal with
this the components have been moved to their own packages and state/rpc
classes will be defined in their own Java files.