aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update Chrome version check to 85 (#12090) (#12102)8.11.38.11Anna Koskinen2020-09-0910-1/+7
| | | | * Update Chrome version check to 85 (#12090)
* Update ServletPortletHelper.java (#12087) (#12100)Anna Koskinen2020-09-071-0/+4
| | | | | 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. Authored-by: Clemens von Schwerin <clemens.vonschwerin@gmail.com>
* Only remove caption margin from the first visible tab. (#12078) (#12099)Anna Koskinen2020-09-073-0/+97
| | | Fixes #10437
* Add 1px buffer to Escalator column natural widths. (#12075) (#12098)Anna Koskinen2020-09-074-7/+7
| | | | | | | | | The purpose of the buffer is to avoid subpixel handling issues, especially when zoomed in or out. In case fractions need to be adjusted for browser compatibility, round up to ensure the contents have the space they need. Fixes #12048
* Fix to natural column width calculations in Table footer. (#12074) (#12097)Anna Koskinen2020-09-071-1/+1
|
* Add a regression test for Table's RowGenerator feature. (#12069) (#12071)Anna Koskinen2020-08-112-1/+168
| | | | There used to be a TB2 test for this once upon a time, but for some reason that never got converted into a TB3 test before getting removed.
* Explicitly remove old dataprovider listener when new one is set (#12064) ↵8.11.2Anna Koskinen2020-08-101-7/+35
| | | | | | | | | | (#12067) * Explicitly remove old dataprovider listener when new one is set (#12064) If not done, this can cause memory leakage Fixes: #12065
* Fix possible NPE with MPR (#12040) (#12066)Anna Koskinen2020-08-102-5/+17
| | | | | | | | * Fix possible NPE with MPR (#12040) 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
* Revert 'Rewrote debouncing of onResize (#11899)' (#12051) (#12056)Anna Koskinen2020-07-153-33/+256
| | | Fixes #12049
* Add support for "ww" in date format (#12037) (#12052)Anna Koskinen2020-07-143-1/+77
| | | | | | | 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 Authored-by: Tatu Lund <tatu@vaadin.com>
* Update release-note template8.11.1Zhe Sun2020-07-021-4/+4
|
* Cherry pick 8.11.1 (#12046)Zhe Sun2020-07-0111-11/+337
| | | | | | | | | | | | | | | | | | | * Fix rendering of TreeGrid's frozen columns after hierarchy-column reset (#12028) * Add tests * Fix getVisibleFrozenColumnCount() if SelectionMode is multi * Update ComboBox popup position comparison to use correct top value. (#12041) Fixes #12029 * Clear thread local instances on connection lost in push handler (#12042) Adopted from https://github.com/vaadin/flow/pull/8567 Co-authored-by: Tarek Oraby <42799254+tarekoraby@users.noreply.github.com> Co-authored-by: Anna Koskinen <Ansku@users.noreply.github.com> Co-authored-by: Tatu Lund <tatu@vaadin.com>
* Use Rebase and Merge, Please (#12023)8.11.0Zhe Sun2020-05-2685-41/+593
|
* Update release-notes.htmlZhe Sun2020-05-261-9/+9
|
* Fix to compatibility Grid sorting after removing multi-select. (#12012) (#12013)Anna Koskinen2020-05-153-17/+108
| | | | | | * Fix to compatibility Grid sorting after removing multi-select. (#12012) Adapted from V7 fix #10999
* Fixed error message to use given parameters. (#12008) (#12011)Anna Koskinen2020-05-151-4/+5
| | | Fixes #11993
* Catch exception that is thrown when Grid is scrolled during operation ↵Anna Koskinen2020-05-151-7/+13
| | | | | | | (#12002) (#12009) IllegalStateException may occur if user has scrolled Grid (compatibility library version) so that Escalator has updated, and row under Editor is no longer there Issue #11463
* Removing deprecated parameter (#12004) (#12007)Anna Koskinen2020-05-141-2/+1
| | | | | Fixes: https://github.com/vaadin/framework/issues/11958 Authored-by: Tatu Lund <tatu@vaadin.com>
* Fix indexing issue in Compatibility Grid resize when scrolled to bottom. ↵Anna Koskinen2020-05-142-0/+35
| | | | | (#12003) (#12006) Issue #11893
* Update firefox version to 75 (#12000) (#12005)Anna Koskinen2020-05-141-1/+1
| | | Authored-by: Zhe Sun <31067185+ZheSun88@users.noreply.github.com>
* Updated release-notes.html (#11998)8.11.0.beta1Anna Koskinen2020-05-121-5/+6
| | | | * Updated release-notes.html
* Support for javax.validation @NotEmpty annotation. (#11985) (#11997)Anna Koskinen2020-05-121-1/+2
| | | | | | * Support for javax.validation @NotEmpty annotation. (#11985) Fixes #10914
* Update release note for 8.11 betaZhe Sun2020-05-121-1/+1
|
* Refresh DataProvider only once when reordering the grid using GridRowDragger ↵Martín López2020-05-112-1/+25
| | | | | (#11981) Fixes #10844
* Removed unused parameter from DataNode creation (#11976)James Pether Sörling2020-05-111-2/+1
| | | Fixes #11958
* Fixed a problem with example code in article "Letting The User Download A ↵Martín López2020-05-081-2/+9
| | | | | File" (#11971) Fixes #10580
* Fix RTA's CreateLink in Firefox & IE11 (#11979)Tarek Oraby2020-05-083-1/+140
| | | | | | | 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. (#11980)Anna Koskinen2020-05-053-7/+217
| | | | | | * Take overlays into account in getConnectorForElement. Fixes #11212
* Allow replacing all columns at once when some of them are frozen. (#11978)Anna Koskinen2020-04-303-2/+89
| | | Fixes #11824
* Fix the column width calculations for full width cell contents. (#11974)Anna Koskinen2020-04-293-0/+180
| | | Fixes #11973
* Fix hiding / un-hiding with frozen columns in multiselect mode (#11972)Tatu Lund2020-04-281-4/+4
| | | | | | | 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. (#11956)Anna Koskinen2020-04-243-2/+162
| | | | | | * Don't center a window that has already been removed. Fixes #11942
* Add missing since tag (#11957)8.11.0.alpha1Zhe Sun2020-04-233-9/+9
|
* Updating release notes (#11955)Tatu Lund2020-04-231-6/+10
| | | | | * Updating release notes * Fixing typo
* Fix incorrect position of column selector in MPR (#11953)Tatu Lund2020-04-213-3/+7
| | | | Cherry pick from https://github.com/vaadin/framework/pull/11946
* Add asMultiSelect() to Tree class (#11949)Tarek Oraby2020-04-211-0/+12
| | | | | 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
* Fixed the JavaDoc (#11950)Vesa Nieminen2020-04-211-2/+2
| | | | | 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
* Allow AbstractDateField to provide DST zone names over custom ranges (#11927)Tarek Oraby2020-04-214-10/+461
| | | | | | | | | 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
* Add methods to control validation (#11945)Tatu Lund2020-04-213-10/+205
| | | | | | | | | - 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>
* Add multiselect column compensation (#11951)Tatu Lund2020-04-201-1/+5
|
* Updating Chrome version (#11952)Tatu Lund2020-04-161-1/+1
|
* Update Liferay kernel version (#11943)Tatu Lund2020-04-091-1/+1
| | | | | 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
* Expired session: use 403 Forbidden instead of 410 Gone (#11859)Felix Fontein2020-04-083-9/+16
| | | Use 403 Forbidden instead of 410 Gone when session expired. Also prevent caching in more cases.
* Set DateField value only if it passes range check (#11887)Tatu Lund2020-04-084-20/+51
| | | Fixes #11108
* Determine Push transport before re-connect (#11884)Tatu Lund2020-04-071-9/+6
| | | | | | | | | 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
* Update hibernate dependency (#11905)Tatu Lund2020-04-071-1/+1
| | | | | 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
* Remove unnecessary null-check at ValueContext constructors (#11915)Konstantin Kuzmin2020-04-071-5/+0
|
* Added missing blank line, which fussed up the text (#11935)thigg2020-04-071-0/+1
|
* Change to using StringBuilder (#11941)Hk-tang2020-04-061-2/+2
| | | Should use a StringBuilder to accumulate strings in a loop, to avoid the performance cost of repeatedly constructing strings.
* Fix sanitization of empty RTA input for Firefox & IE (#11937)Tarek Oraby2020-04-061-2/+2
| | | | | | | Browsers differ in what they return as the content of a visually empty rich text area (RTA). Accordingly, RTA sanitizes these different values ensuring an empty string is returned to the framework. However, existing sanitization criteria doesn't work for Firefox 74 and Internet Explorer 11. This fix appends the sanitization criteria of Firefox 74 and IE 11, ensuring an empty string is returned to the framework for a a visually empty RTA. Closes #10338