| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
Without access to the presentation provider used for a column, it is often not possible to reconstruct the data as shown on the end-user's screen
This commit adds a getter method to Grid.Column to allow access to this provider
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix to LayoutManager size calculations during transform.
- ComputedStyle is slower but more reliable than using
getBoundingClientRect, which does not work as expected if a transform
has been applied to the element or one of its parents. This is a problem
e.g. with PopupView, where getBoundingClientRect will return too small
size (or even zero size) for all the popup contents while the opening
animation is active. ComputedStyle ignores the transform and returns the
expected value.
- The presence of the element in DOM must be checked before the size is
requested from ComputedStyle, if the element has disappeared from DOM
without a warning and calculation is attempted anyway, the browser gets
stuck.
- Possibility to configure LayoutManager to use the less reliable
calculations for applications where the slight performance difference is
more important than layout issues within elements that have transform
animations.
- Manual test, problem isn't reproducible by TestBench.
Fixes: #11187
|
|
|
|
|
|
|
| |
- Informative error message
- Reset back to disabled state when enabling fails
- Incorrect usage also detectable using non-mobile devices
Fixes #12152
|
|
|
| |
See: https://vaadin.com/forum/thread/15931682
|
|
|
|
|
| |
Lambdas and function references do not serialize
See: https://vaadin.com/forum/thread/18462951/vaadin-8-stateful-session
|
|
|
| |
Fixes: https://github.com/vaadin/multiplatform-runtime/issues/77
|
|
|
|
|
|
| |
polling an obsolete resource (#12115)
https://github.com/vaadin/framework/issues/12113
|
| |
|
| |
|
| |
|
|
|
|
| |
(#12091)
|
|
|
| |
Fixes: https://github.com/vaadin/framework/issues/7773
|
|
|
| |
This is needed to get /UIDL working behind a reverse proxy. Without the change pathInfo would be "/UIDL" but prefix would be "/UIDL/" in line 105.
|
| |
|
|
|
|
|
| |
Hibernate Validator 5+ requires
- Validation API 2+
- explicit Expression Language dependency
|
|
|
| |
Fixes #11235
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Explicitly remove old dataprovider listener when new one is set
If not done, this can cause memory leakage
* Formatting
* Fixed coding style
* Take into account further scenarios
Component maybe detached permanently and thus data provider listener needs to be remove in detach. Also if this is only momentary remove from layout add back cycle, re-setup is needed in attach, in case it was not already setup before attaching by setDataProvider.
* Change super.detach() call order
* Added null check to getDataProvider
* Setting dataProviderListener to null on detach
* Removing listener only if it exists
* Fix
|
|
|
|
|
| |
It is possible when Vaadin 8 is used with MPR, that ui.getCurrent().getSession() returns null.
See: https://github.com/vaadin/multiplatform-runtime/issues/5
|
|
|
|
|
| |
Calculate number of the week in the year based on Date. Note, support for "ww" is missing from GWT DateTimeFormat and java.util.Calendar is not supported in GWT, hence DIY method is needed.
Fixes: #10603
|
| |
|
|
|
| |
Adopted from https://github.com/vaadin/flow/pull/8567
|
|
|
| |
Fixes #11993
|
|
|
|
|
|
| |
* Removing deprecated parameter
Fixes: https://github.com/vaadin/framework/issues/11958
|
| |
|
|
|
| |
Fixes #10914
|
|
|
|
|
| |
(#11981)
Fixes #10844
|
|
|
| |
Fixes #11958
|
| |
|
|
|
|
|
| |
Tree class doesn't currently provide an obvious way that would enable a Tree object to be treated as a multi select. This commit extends the Tree API, enabling it to be used as a multi select, which would importantly facilitate the selection/deselection of multiple items in trees whose SelectionMode is MULTI.
closes #11948
|
|
|
|
|
| |
HierarchyMapper. getParentIndex() method has a different JavaDoc from the HierarchicalDataCommunicator. This is a simple fix for that.
https://github.com/vaadin/framework/blob/master/server/src/main/java/com/vaadin/data/provider/HierarchyMapper.java#L96
|
|
|
|
|
|
|
|
|
| |
DateTimeField and DateField currently implement a hardcoded logic by which they adjust their time zone names to display daylight-saving time (DST) zone names. Specifically, this hardcoded logic only adjusts the displayed date to DST format if that date falls in one of the years between 1980 and the following 20 years in the future from the current date (that is, until 2040 at the time of this commit).
For some use cases, this is problematic because it is desirable to display proper DST-adjusted time zones beyond the 20 years limit (and possibly also before 1980).
Rather than choosing another arbitrary, hardcoded threshold, this commit extends the AbstractDateField API to allow the user to choose the range (start and end years) between which the DST transition dates are calculated (and hence displayed properly). If the user doesn't invoke this new API, DateTimeField and DateField will default to behave according the existing logic (i.e. display DST zone names between 1980 and 20 years into the future).
Closes #11919
|
|
|
|
|
|
|
|
|
| |
- Enable / disable all validators on Binder level
- Enable / disable validators on Binding level
- add writeBeanAsDraft(bean,boolean) for writing draft bean with validators disabled
Fixes https://github.com/vaadin/framework/issues/10709
Co-authored-by: Zhe Sun <31067185+ZheSun88@users.noreply.github.com>
|
|
|
|
|
| |
Liferay 7.3 series have kernel version 10.x, i.e. limit needs to be extended from 10 -> 11
Fixes: https://github.com/vaadin/framework/issues/11938
|
|
|
| |
Use 403 Forbidden instead of 410 Gone when session expired. Also prevent caching in more cases.
|
|
|
| |
Fixes #11108
|
|
|
|
|
|
|
|
|
| |
onConnect was allways called with websocket = false. I think this is wrong, since if there was connection loss in websocket, now connection cannot be re-established in websocket mode.
Fixes: https://github.com/vaadin/framework/issues/11299
This bug may have been manifesting in other ways as well
Recently similar fix was done in Flow as well, see: https://github.com/vaadin/flow/pull/7489
|
| |
|
|
|
| |
Should use a StringBuilder to accumulate strings in a loop, to avoid the performance cost of repeatedly constructing strings.
|
|
|
| |
Fixes #11810
|
|
|
| |
Fixes #10419
|
|
|
| |
Fixes #11806
|
|
|
|
|
|
|
|
| |
* Added note to DateField#setRangeStart JavaDoc
* Added additional checking of valid startDate
* Reverted previous commit
|
|
|
| |
Fixes: https://github.com/vaadin/framework/issues/11875
|
|
|
|
|
| |
* Update to 8.11-SNAPSHOT
|
|
|
|
|
| |
Fixes: https://github.com/vaadin/framework/issues/9933
Cherry pick from: https://github.com/vaadin/flow/pull/7317
|
|
|
|
|
|
|
|
|
|
| |
* Making setEditable friendlier
The current behavior is not buggy, so this PR is an enhancement
Fixes https://github.com/vaadin/framework/issues/8718
* Improved JavaDoc
|
|
|
|
|
|
| |
* Added notes in JavaDoc of TEXTFIELD_INLINE_ICON
Fixes https://github.com/vaadin/framework/issues/10752 and https://github.com/vaadin/framework/issues/9089
|
| |
|