| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
Fixes #10435
|
| |
|
|
|
| |
Handle possible race condition by disabling the editor's widget while awaiting validation from the server.
Fixes #12270
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add browser specific handling in setRows
Fixes: https://github.com/vaadin/framework/issues/10138
Fixes: https://github.com/vaadin/framework/issues/7878
* Enforced minimum height to 1 rows and added a test.
Co-authored-by: Anna Koskinen <anna@vaadin.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- Added check for touch move event in order to allow the same flow for
both mouse and touch events when dragging a Window by its header.
- Can be tested with SubwindowDraggability class.
Fixes #12257
Co-authored-by: Jakub Antoniak <j.antoniak8@gmail.com>
|
| |
|
|
| |
* Add ErrorHandler to AbstractTestUI
|
| |
|
| |
This reverts commit 8c39731123b56ef5fa08a614b9aa1b55bd53e5cc.
|
| | |
|
| |
|
| |
Avoids dependency security alert
|
| |
|
|
|
| |
- Override ParallelRunner of TestBench 5.2.0 for uitest module in order
to intercept and log uncaught exceptions in
TBMethod.invokeExplosively(...).
|
| | |
|
| |
|
| |
#12132 fixed an old bug, conversion was not done back, which was a regression from Vaadin 7. However since the bug has been present long time, it has become established behavior, thus there may be need to disable conversion back to presentation sometimes, thus this API as added.
|
| | |
|
| |
|
| |
Fixes: https://github.com/vaadin/framework/issues/12240
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Fix updating Escalator's physical row index.
- Physical index should take into account that more than one row can
have a spacer. Physical index has no practical effect on how Grid looks
like or behaves, since Escalator by design operates independently of it
and the visual positioning of elements is based on the logical and
visual indices. Physical index only affects the order of elements
within the DOM tree, where a mismatch can cause confusion during
debugging.
|
| |
|
|
|
|
|
|
|
|
| |
- Old details should close.
- New details should open.
- If some row has details in both old and new item set, the details row
contents should get updated.
- Updating details row contents should not break the positioning of the
rows and details below.
Fixes #12211
|
| |
|
| |
Fixes: https://github.com/vaadin/framework/issues/12207
|
| | |
|
| |
|
|
| |
* Update copyright year range.
|
| | |
|
| |
|
|
|
| |
- These plugins cause significant problems for many Windows developers,
and since most active maintainers are currently included in that group,
the plugins have been deemed more trouble than they are worth.
|
| |
|
|
|
|
|
|
| |
* Fix displaying checkboxes within Grid editor row.
- Checkbox margins should match regular row content margins.
- Multiselect checkbox label should only be visible for assistive
devices.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- null check to prevent NPE from the merged column headers
- convert to internal columnIds for merge handling
- use correct cell in merge handling
- switch away from streams in merge handling for easier readability
- regression test
Fixes: #10464
|
| |
|
|
|
|
|
| |
(#12168)
Do not fire DateField's value change event if the new date is not within the range.
Fixes: #12163
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(#12199)
* Clear out ClientCache when UI is detached to prevent a minor memory leak
Implemented with a listener rather than direct call from UI.detach() in
order to avoid new public API, since the whole feature has been marked
for removal. This doesn't yet prevent the cache or the type map from
getting slightly bloated during the UI's lifetime.
See: #3705
|
| | |
|
| | |
|
| |
|
| |
Leftover from https://github.com/vaadin/framework/commit/0081286c8d05c3751803181230092bd4b1e769f7
|
| |
|
|
|
|
| |
This hardens the framework against a theoretical timing attack based on
comparing how quickly a request with an invalid CSRF token is rejected.
Cherry-picked from: https://github.com/vaadin/flow/pull/9875
|
| |
|
|
|
|
|
|
|
| |
This is the same as https://github.com/vaadin/framework/pull/12188,
but also applied for the upload security key
and the push id since both of those are also used to protect against
cross-site attacks. In addition, documentation for the push id is
clarified to point out its role.
Cherry-picked from: https://github.com/vaadin/flow/pull/9896
|
| | |
|
| | |
|
| |
|
|
|
| |
https://github.com/vaadin/framework/pull/12043 changed resync message sending to be deferred to queue. Now also the setting of the semaphor in message handler needs to be deferred to its right place. Otherwise there is possibility for a timing glitch. I.e. MessageHandler is set to resync handling mode before message is actually send.
Fixes: https://github.com/vaadin/framework/issues/12151
|
| |
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
* Test tweaks
- Divided HeaderFooterClickLeftRightMiddleTest tests to separate methods
based on click type
- Updated screenshot
|
