summaryrefslogtreecommitdiffstats
path: root/uitest
Commit message (Collapse)AuthorAgeFilesLines
* Update Chrome version check to 85 (#12090)Anna Koskinen2020-09-0210-1/+7
|
* Add API to detect if GridMultiSelect select-all checkbox is checked (#12086)Tarek Oraby2020-08-262-0/+79
|
* fix for #12079 - recalculate Composite layout inside Window (#12082)Olli Tietäväinen2020-08-262-0/+136
| | | Co-authored-by: Anna Koskinen <anna@vaadin.com>
* Only remove caption margin from the first visible tab. (#12078)Anna Koskinen2020-08-192-0/+89
| | | Fixes #10437
* Add 1px buffer to Escalator column natural widths. (#12075)Anna Koskinen2020-08-173-0/+0
| | | | | | | | | | | | * Add 1px buffer to Escalator column natural widths. 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
* Add a regression test for Table's RowGenerator feature. (#12069)Anna Koskinen2020-08-111-0/+167
| | | | | | | * Add a regression test for Table's RowGenerator feature. 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.
* Add column width recalculation when vertical scrollbar hidden/shown. (#12058)Anna Koskinen2020-07-233-4/+10
| | | | | - 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.
* Revert 'Rewrote debouncing of onResize (#11899)' (#12051)Anna Koskinen2020-07-093-4/+243
| | | Fixes #12049
* All updates to Escalator size should get reported to LayoutManager. (#12050)Anna Koskinen2020-07-082-0/+204
| | | | Delayed size changes caused by added or removed scrollbars should be taken into account.
* Add support for "ww" in date format (#12037)Tatu Lund2020-07-031-0/+1
| | | | | 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
* Ensure type safety and serializable nature of all the listeners (#12045)Tatu Lund2020-07-031-1/+2
|
* Update ComboBox popup position comparison to use correct top value. (#12041)Anna Koskinen2020-06-262-1/+36
| | | Fixes #12029
* Fix rendering of TreeGrid's frozen columns after hierarchy-column reset (#12028)Tarek Oraby2020-06-182-0/+115
| | | | | * Add tests * Fix getVisibleFrozenColumnCount() if SelectionMode is multi
* Update chrome version to 83 (#12024)Zhe Sun2020-05-2663-1/+1
| | | | | | * Update chrome version to 83 * Update screenshots
* Fix ComboBox in read-only mode allowing value change by user (#12022)Tarek Oraby2020-05-252-0/+71
| | | | | | | | | * 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>
* Fix compatibility ComboBox filtering when page length is zero. (#12016)Anna Koskinen2020-05-202-0/+117
| | | Issue #11246, slightly modified cherry-pick from #11247
* Fix scrolling problem in table in Chrome 56+ (#12015)Anna Koskinen2020-05-192-0/+134
| | | | | | * Fix scrolling problem in table in Chrome 56+ Issue #8707, slightly modified cherry-pick of #10492
* Table / TreeTable multiselect disabling of touch detection (#12014)Anna Koskinen2020-05-195-1/+185
| | | | | | | | 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
* Fix to compatibility Grid sorting after removing multi-select. (#12012)Anna Koskinen2020-05-152-0/+75
| | | Adapted from V7 fix #10999
* Fix indexing issue in Compatibility Grid resize when scrolled to bottom. ↵Anna Koskinen2020-05-131-0/+34
| | | | | (#12003) Issue #11893, cherry-pick from #11984
* Update firefox version to 75 (#12000)Zhe Sun2020-05-131-1/+1
|
* Update to 8.12-snapshot (#11995)Zhe Sun2020-05-131-1/+1
|
* Fix RTA's CreateLink in Firefox & IE11 (#11979)Tarek Oraby2020-05-082-0/+115
| | | | | | | 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-052-0/+193
| | | | | | * Take overlays into account in getConnectorForElement. Fixes #11212
* Allow replacing all columns at once when some of them are frozen. (#11978)Anna Koskinen2020-04-302-0/+78
| | | Fixes #11824
* Fix the column width calculations for full width cell contents. (#11974)Anna Koskinen2020-04-292-0/+140
| | | Fixes #11973
* Don't center a window that has already been removed. (#11956)Anna Koskinen2020-04-242-0/+154
| | | | | | * Don't center a window that has already been removed. Fixes #11942
* Fix incorrect position of column selector in MPR (#11953)Tatu Lund2020-04-211-0/+0
| | | | Cherry pick from https://github.com/vaadin/framework/pull/11946
* Allow AbstractDateField to provide DST zone names over custom ranges (#11927)Tarek Oraby2020-04-212-0/+340
| | | | | | | | | 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
* Updating Chrome version (#11952)Tatu Lund2020-04-161-1/+1
|
* Set DateField value only if it passes range check (#11887)Tatu Lund2020-04-082-1/+6
| | | Fixes #11108
* Allow setting Upload button caption as HTML, move data to SharedState. (#11940)Anna Koskinen2020-04-062-0/+107
| | | Fixes #11810
* Prevent upload if no file is selected. (#11939)Anna Koskinen2020-04-0319-2/+191
| | | Fixes #10419
* Ensure ChangeListener still works after first upload. (#11936)Anna Koskinen2020-04-012-0/+121
| | | Fixes #10420
* Ensure recalculateColumnWidths works with refreshAll. (#11934)Anna Koskinen2020-03-312-0/+155
| | | | | | | | Column widths shouldn't be calculated between the clearing of cache and re-populating it, but be delayed until the cache has some content again. The calculations should only be triggered immediately if no rows are expected. Fixes #9996
* Updated LayoutTester screenshots for IE and FF. (#11930)Anna Koskinen2020-03-27164-0/+0
| | | | * Updated LayoutTester screenshots for IE and FF.
* Fix an issue with frozen column count and unhiding. (#11929)Anna Koskinen2020-03-262-0/+78
| | | | | | | * Fix an issue with frozen column count and unhiding. Unhiding logic should take into account that there can be hidden frozen columns that are not the column currently getting shown.
* Add setters to Criterion to fix serialization. (#11926)Anna Koskinen2020-03-261-0/+59
| | | Fixes #11909
* Tweaked layouttester tests to be more informative. (#11800) (#11813)Anna Koskinen2020-03-23132-33/+495
|
* Trigger re-measure after updating ElementResizeListeners. (#11912)Anna Koskinen2020-03-092-0/+66
| | | | | | | | | | | Removing ElementResizeListeners from an element makes it unmeasurable and clears any saved measured values. Adding the listeners back makes the element measurable again but doesn't add it to measuring queue. Measuring needs to happen or any updates to expanded components within a layout (without changes that would trigger full re-measuring of the layout itself) lead to broken expand size calculations with any fixed size elements assumed to have no size. Fixes #10734
* Further tweaks to ComboBox popup positioning. (#11910)Anna Koskinen2020-03-062-0/+67
| | | | | | | | * Further tweaks to ComboBox popup positioning. - Updated a comment and renamed a private method for better clarity. - Blocked unnecessary position updates. - Added a test for #11866 / #11894.
* Removing code causing the trouble (#11898)Tatu Lund2020-02-242-0/+26
| | | | | | | | | | | | | | | | | | * Removing code causing the trouble Removing code that was apparently not needed in previous fix and caused regression Fixes: https://github.com/vaadin/framework/issues/11895 * Added feature to test UI * Added test case * Adding missing import * Fixing test UI * Enable DateField
* Update Chrome version (#11891)Tatu Lund2020-02-181-1/+1
|
* Fix logic of lexicographical comparison of DateField range end (#11885)Tatu Lund2020-02-131-0/+46
| | | | | | | | | | | | | | | | | | | | | | * Fix logic of lexicographical comparison of DateField range end Fix logic of lexicographical comparison of DateField range end with large year numbers ( > 9999) Fixes #11881 * Added tests Purpose of dateFieldRangeYearDigitsIncrease() is to test that rangeEnd works correctly on 4 to 5 digits change boundary Purpose of dateFieldRangeYearBigNumbersPopupOpens() is to test that popup opens also when there is more than 4 digits in year * Fixing typo * Add error message * Set the date of the field in test * Fixing
* Don't reset date to current at DateField state (e.g. read-only) updates. ↵Anna Koskinen2020-01-282-0/+87
| | | | | | | | | (#11879) - DateFields with month or year resolution should not get their date reset to current date if the field's state is updated (e.g. by changing read-only status or adding a range). Fixes: #11864, #11605
* Update to 8.11 snapshot (#11874)Zhe Sun2020-01-161-1/+1
| | | | | * Update to 8.11-SNAPSHOT
* Ensure value change happens before shortcuts in compatibility components ↵Anna Koskinen2020-01-152-0/+86
| | | | | (#11871) Fixes #10854
* Convert DateTimeFieldReadOnlyTest to not rely on screenshots. (#11870)Anna Koskinen2020-01-1313-16/+45
|
* Convert DateFieldReadOnlyTest to not rely on screenshots. (#11867)Anna Koskinen2020-01-1013-16/+45
|
* Removed outdated spacer height update from removal process. (#11861)Anna Koskinen2020-01-092-0/+115
| | | | | | * Removed outdated spacer height update from removal process. Fixes #11856
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-16 00:00:27 +0000