| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
(#11799)
There is a bug in TwinColSelect loging, it retains selection by indexes not by values after being sorted when new item has been added. This is a fixed by changing updateListBox method to retain the selection as it is being called after selection is being done.
Fixes: #11287
|
|
|
|
|
|
| |
* Eliminate un-intuitive NPE
Fixes https://github.com/vaadin/framework/issues/10947
|
|
|
|
|
|
|
|
|
|
| |
* Cherry picks of Binder fixes in Flow
Addresses: https://github.com/vaadin/framework/issues/9000
Addresses: https://github.com/vaadin/framework/issues/11109
These changes are adopted from https://github.com/vaadin/flow/pull/4138 and https://github.com/vaadin/flow/pull/6757
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- If an open popup is reset to its default position on every update from
the server before getting adjusted again to the actual expected
position, on heavier applications some of those intermediate positions
might get rendered. If the ComboBox is positioned at the right edge and
the popup contents are longer than the input field (i.e. popup should
open to the left, not right) this might cause flickering.
- Setting the default position is only actually needed when the popup is
opened in order to give it a baseline, otherwise it's better to simply
adjust the position if needed.
Continues on #11718
|
|
|
|
|
|
| |
* Added missing constructor with scanNestedDefinitions option
Addresses https://github.com/vaadin/framework/issues/10949
|
|
|
|
|
|
|
|
|
|
| |
The Vaadin session itself is also stored in APPLICATION_SCOPE. The default
scope is PORTLET_SCOPE, so lock would be otherwise not be in sync with
the session.
To be able to do this, relevant methods in VaadinService are made protected so
that VaadinPortletService can override them.
Fixes #11611
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fixing issue with Push stopping working in some circumstances
If new request is attempted when resynchronization is ongoing, the Push will stop working. This patch fixes the issue by aborting handleJson if resynch is already ongoing.
This PR supercedes https://github.com/vaadin/framework/pull/11786
Fixes #11702, #7719
* Call onResynchronize() in MessageHandler
* Optimizing
|
|
|
|
|
|
|
|
| |
The checkbox for selecting all rows only selects all the rows that have
not been filtered out. Changing the filtering does not change the
selection or the checkbox state so assuming that all rows are selected
simply because the checkbox has been checked cannot work.
Fixes #11479
|
| |
|
|
|
| |
Addresses https://github.com/vaadin/framework/issues/1262
|
|
|
|
|
|
| |
The filtering needs to be delayed, otherwise it's performed before the
new filter text is available and the old filter text is used instead.
Fixes #11779
|
|
|
|
|
|
|
|
|
|
|
|
| |
- If the Grid has frozen columns zooming can cause the regular column
cells to be ever so slightly out of sync with their corresponding rows.
This difference is not noticeable to naked eye but is big enough that
it's possible to hover over the row instead of the cell, which causes an
assertion error and a big ugly error popup. Switching to logging retains
the information delivered by the assertion error for developer purposes
but makes the end user experience smoother.
- Can be tested manually with GridColumnFrozenColumn test UI.
Fixes #11198
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added 1px tolerance to ScrollbarBundle's internal sanity check.
Requiring exact match can cause this check to fail when the browser is
zoomed since rounding is involved. This can in turn block some features
like opening of Grid Editor from working until some more scrolling
happens and the minute inconsistency is fixed.
Can be tested manually using GridEditorUI, depending on the environment
different amounts of zooming may be required for the problem to
manifest.
Fixes #11672
|
|
|
|
|
|
|
|
| |
- The new top row logical index should always be within the logical
range and high enough up to avoid leaving a gap if possible.
- Added regression testing for using the different scroll destination
types for scrolling to the top and to the bottom by index.
Fixes #11732
|
|
|
|
|
| |
And corrected couple of typos
Addresses https://github.com/vaadin/framework/issues/11492
|
|
|
|
|
| |
- Row index counts up from zero, data provider size counts up from one,
as one would expect. If the two match we are already past the available
range.
|
|
|
| |
Addresses https://github.com/vaadin/framework/issues/11520
|
| |
|
| |
|
|
|
|
|
| |
(#11755)
Fixes #11718
|
|
|
|
|
|
|
|
| |
* Make sure expanding/collapsing updates expected cache size.
Fixes #11749
* Merge branch 'master' into issue11749
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Checking the push configuration outside of session lock threw
an AssertionError, so the push configuration is not checked anymore.
- The original problem with cancelling Upload was due to a subtle
ordering issue that depended on the Push configuration.
In the case of PushMode.AUTOMATIC, a new StreamVariable was
added by the `Upload` component _before_ the `FileUploadHandler`
got a chance to remove the old `StreamVariable`. As a result, the
`FileUploadHandler` actually removed the fresh `StreamVariable`,
breaking future uploads.
Fixes #11682
|
|
|
| |
Addresses https://github.com/vaadin/framework/issues/10277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Upload should preserve MIMEType after first selection
Fix #11698
Automated test is not run locally, need to continue with it
* Remove unused imports
* Add sleep time in testing purposes
* Getting a new instance of an input, after file is downloaded
Exclude IE from tests. Throws https://stackoverflow.com/questions/23883071/unhandled-alert-exception-modal-dialog-present-selenium , but checked manually and it works
|
|
|
| |
Change-Id: Iea13b958356b0246586bcb7e9969bc26db43bb96
|
|
|
|
|
|
|
|
| |
* Catch and handle IllegalStateException
Fixes https://github.com/vaadin/framework/issues/11730
* Renaming variables
|
|
|
|
|
|
|
|
|
|
| |
* Added note in JavaDoc of removeColumn
https://github.com/vaadin/framework/issues/11722
* Merge branch 'master' into fix11722
* Merge branch 'master' into fix11722
|
| |
|
|
|
|
|
|
|
|
| |
* Update Chrome version to 77
* update screenshots
* update screenshots
|
|
|
|
|
|
| |
* Update release note to mention Java 11 support
* Update explanation about client side code
|
|
|
|
|
|
|
| |
(#11710)
Removal of data communicator needs to happen before call to super.remove() since super.remove() sets parent to null causing the NPE.
Fixes https://github.com/vaadin/framework/issues/11617
|
|
|
| |
Fixes https://github.com/vaadin/framework/issues/11701
|
|
|
| |
"doesn't not" should be either "doesn't" or "does not".
|
|
|
|
|
|
|
|
|
|
|
| |
- Initial implementation erroneously assumed that
ScrollDestination.START would only be used for scrolling up and
ScrollDestination.END for scrolling down. That's obviously not what they
are for, otherwise everyone would be using ScrollDestination.ANY.
- Moved actual scrolling to within the helper method that originally
only calculated the new scroll position. Parent method became too long
otherwise.
Fixes #11706
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated row and spacer handling for Escalator.
Main changes:
- Spacers are only maintained and checked for rows that have DOM
representation, and not at all if there is no details generator. This
gives notable performance improvements to some particularly large Grids
- Escalator no longer tries to trim away any rows that don't fit within
the viewport just because a details row gets opened in Grid. This leads
to some increase in simultaneous DOM elements, but simplifies the logic
considerably. For example opening or closing details rows doesn't
require checking the overall content validity beyond the details row
itself anymore, but some repositioning at most. There are also no longer
any orphaned spacers without corresponding DOM rows.
- Spacers are better integrated into the overall position calculations.
- Some public methods that are no longer used by Escalator or have
changed functionality or order of operations. Any extending classes that
tap into row, spacer, or scroll position handling are likely to need
reworking after this update.
- Auto-detecting row height is delayed until Escalator is both attached
and displayed.
|
|
|
|
|
|
|
|
|
|
|
| |
* Read-only styles shouldn't override borderless background styles.
- Fixed for ComboBox and DateField styles, other tested components
already do it right.
Fixes #11671
* Merge branch 'master' into issue11671
|
|
|
|
|
|
|
|
| |
* Add explicit handling of ctrl-a
Fixes https://github.com/vaadin/framework/issues/11678
* Adds test case and formatting the code
|
| |
|
|
|
| |
Fixes https://github.com/vaadin/framework/issues/11409
|
|
|
|
| |
* Update the since tag
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Apply offset to column index depending on presense of selection column
After testing this manually I noticed that offset correction needs to be negative
* Add the testing UI
|
|
|
|
|
|
|
|
|
| |
succeedL… (#11655)
* Ensure the upload button has been disabled when calling from succeedListener with Push enabled
* Add Tests to verify
|
|
|
| |
Fixes #10339
|
| |
|
|
|
|
| |
* Use https for Maven repositories
|
|
|
| |
Fixes #10741
|
|
|
|
|
|
| |
- Escalator should notify when an existing details row is moved to a new
index.
- Grid and DetailsManagerConnector should update their internal indexing
when details manager index changes in Escalator.
|
|
|
|
|
|
| |
* Fixes #11642. ComboBox with pageLength 0 should be updated if DataProvider changes
* added comments, fixed imports
|