| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
There might be pending requests in the queue when a resync request is
made (e.g. through a theme change). This can cause conflicts if the
resync request is handled immediately. Therefore the resync request
should also be added to the queue and only get resolved when
doSendInvocationsToServer() gets triggered again.
Fixes #11954
|
|
|
|
|
| |
- If the Grid has any columns with non-fixed widths, the presence of a
vertical scrollbar affects the column width calculations. Horizontal
scrollbar should only be shown when actually needed.
|
|
|
| |
Fixes #12049
|
|
|
|
| |
Delayed size changes caused by added or removed scrollbars should be
taken into account.
|
|
|
|
|
| |
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 #12029
|
|
|
|
|
| |
* Add tests
* Fix getVisibleFrozenColumnCount() if SelectionMode is multi
|
|
|
|
|
|
| |
* Update chrome version to 83
* Update screenshots
|
|
|
|
|
|
|
|
|
| |
* Fix ComboBox in read-only mode allowing value change by user
Fixes #12021
* Fix popup hiding condition
Co-authored-by: Tatu Lund <tatu@vaadin.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#12020)
* Add autocomplete prevention to DateField
Autocomplete popup will interfere DateField's own popup
* Adding disableBrowserAutocomplete(..) in WidgetUtil
* Change VComboBox to use WidgetUtil.disableBrowserAutocomplete(..)
* Change to use WidgetUtil.disableBrowserAutocomplete(..)
* Change VFilterSelect to use WidgetUtil.disableBrowserAutocomplete(..)
* Adding WidgetUtil.disableBrowserAutocomplete to VTextualDate
* Adding missing import
* Adding missing import
|
|
|
|
|
|
| |
* Sanitize caption used in compatibility Grid header
Cherry pick of #11644
|
|
|
| |
Issue #11246, slightly modified cherry-pick from #11247
|
|
|
|
|
|
| |
* Fix scrolling problem in table in Chrome 56+
Issue #8707, slightly modified cherry-pick of #10492
|
|
|
|
|
|
|
|
| |
Added a toggle in Table (and thus TreeTable) where you can explicitly
disable multiselect touch screen detection. This allows you to work
around issues on hybrid devices that have both a touch screen and a
keyboard where you don't want automatic simple multiselection applied.
Fixes #11601, slightly modified cherry-pick of #11641
|
| |
|
|
|
| |
Adapted from V7 fix #10999
|
|
|
| |
Fixes #11993
|
|
|
|
|
| |
IllegalStateException may occur if user has scrolled Grid (compatibility library version) so that Escalator has updated, and row under Editor is no longer there
Chrerry pick from https://github.com/vaadin/framework/pull/11467
|
|
|
|
|
|
| |
* Removing deprecated parameter
Fixes: https://github.com/vaadin/framework/issues/11958
|
|
|
|
|
| |
(#12003)
Issue #11893, cherry-pick from #11984
|
| |
|
| |
|
|
|
| |
Fixes #10914
|
|
|
|
|
| |
(#11981)
Fixes #10844
|
|
|
| |
Fixes #11958
|
|
|
|
|
| |
File" (#11971)
Fixes #10580
|
|
|
|
|
|
|
| |
In Firefox and IE11, the 'Create Link' button of the RichTextArea (RTA) only works by turning some highlighted text into a link (by adding the inserted URI as the href property of the text). In that, the RTA in these two browsers behave similarly to the way it does in Chrome and Edge. However, in Firefox and IE11, clicking the 'Create Link' button has no effect if no text is pre-selected by the user. This is different from the button's behavior in Chrome and Edge where the user's provided URI is inserted, both, as the displayed text and its href property if no text is highlighted.
This fix enables the RTA's 'Create Link' button to work consistently across the supported browsers. Specifically, (and in addition to enabling adding the href property of a highlighted text), this fix enables Firefox and IE11 to also insert a new Uri as a text and its href property if no text is already highlighted.
fixes #11888
|
|
|
|
|
|
| |
* Take overlays into account in getConnectorForElement.
Fixes #11212
|
|
|
| |
Fixes #11824
|
|
|
| |
Fixes #11973
|
|
|
|
|
|
|
| |
The previous patch https://github.com/vaadin/framework/pull/11951 did fix the problem (frozen column indicator wrongly positioned) it was meant to, but caused a regression in hiding / un-hiding.
This new fix addresses both problems, i.e. it applies multiselect column compensation in other way, without causing problem in hiding / un-hiding logic
Fixes https://github.com/vaadin/framework/issues/11970
|
|
|
|
|
|
| |
* Don't center a window that has already been removed.
Fixes #11942
|
| |
|
|
|
|
|
| |
* Updating release notes
* Fixing typo
|
|
|
|
| |
Cherry pick from
https://github.com/vaadin/framework/pull/11946
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Vaadin is not affected by CVE-2014-3558, the purpose of the update is avoid false positive alarm.
Fixes: https://github.com/vaadin/framework/issues/11903
|