| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
* Fix wrong year assert in DateField test (#11404)
* Revert "Update Screenshot due to Icon update (#11373)"
This reverts commit b81744ba7b3929c70599d9775d4ffa7a123eb250.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#11370)
Setting read-only state to CheckBoxGroup should disable adding clicking effect. Missing v-readonly style is added to every CheckBox in the component, if it's set to read-only.
Fixes: https://github.com/vaadin/framework/issues/11113
* Add file missed from initial commit
* Verifying that option is enabled
Some of the options might be disabled on there own. Verify that option is not disabled, before removing disabled styles.
* Add missing test file
|
|
|
|
|
|
|
|
| |
* Fixes #10814
* Add missing tests
Fixes #11374
|
|
|
| |
Updated versions to latest ones as people often just copy past things. Added comment to urge people to use the versions they need. Removed version from archetype to use the latest by default.
|
|
|
| |
There are not [source, java] tags.
|
|
|
|
|
|
|
| |
* Update clientsideapp-entrypoint.asciidoc
Adding missing ```[source, java]```
|
|
|
| |
Some snippets codes do not render properly.
|
|
|
|
| |
Update screenshots due to update of search-minus and search-plus icons values
|
|
|
| |
The instructions for applying the license in Designer are wrong and outdated. Remove them.
|
|
|
|
|
|
|
|
|
| |
* Request data update before client response
* fix the accidental commit
* add tests
fixes #11320
|
|
|
|
|
| |
7.1. (#11156)
* This the range might be necessary to increase when Liferay 7.2 or
newer has been released.
|
|
|
|
|
|
|
| |
In certain cases setting the frozen columns didn't produce the expected result in the client side widget state. This happened if the frozen columns value was set to be the same it was before removeAllColumns was called.
This fix removes the frozen column value from the diff state so that the value gets properly set in the client side.
Closes #10653
|
| |
|
|
|
|
|
|
|
|
| |
* Improvements to updating spacer indexes.
- When details rows are moved down, indexes need to be updated from
bottom up.
Fixes #11352
|
|
|
|
|
|
| |
- When rows are added, details row heights need to be taken into account
in positioning.
Fixes #11348
|
|
|
|
|
|
|
|
| |
* Descriptive comment for TwinColSelect - no lazy load #11025
It documents the issue #11025
https://github.com/vaadin/framework/issues/11025#issuecomment-443506307
|
|
|
|
|
|
|
|
|
|
| |
* Fixing dynamic resource registration after activation
* Fixed formatting
* Fixed formatting
* Merge branch 'master' into osgi-dynamic-fix
|
| |
|
|
|
|
|
|
|
| |
* Fix colorPicker tests
In IE11, the click-layer needs longer time to load.
|
|
|
|
|
|
|
|
| |
* Revert "Update ComboBox internal state on new item added (#11094)"
This reverts commit 56ce91c6160a252ddcd952bca6eb7037120ebf59.
* Add tests to verify the issue
|
|
|
|
|
|
| |
* Fix to use correct spacer index and existing helper method.
Fixes #11325
|
|
|
|
|
|
|
|
|
| |
* Fix for setting default row height for a Grid with details row(s) open.
- Details row(s) should be taken into account when the rows are
re-positioned after getting new heights.
Fixes #11325
|
| |
|
|
|
|
| |
* Add javadoc for validate() call in Binder
|
|
|
|
|
|
|
| |
This refactoring addresses two issues cased by dropping updatedData before it was processed. Issues arise , when visibility has change.
Fixes #11274 and similar issue within RadioButton
There is no reliable way to test automatically NativeSelects in Grid, but adding UI test, at least
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit 1ed85caafcc3bead862da4ebbccff1cf912bf505.
|
|
|
|
| |
This reverts commit 77ab4c6da252566dbc7c05046c4488adeb7f970d.
|
|
|
|
|
|
|
|
| |
Fixes #11276
Refactor the code and correct the logic for validation
Rename an internal variable, as it contains more than one type of messages
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Make value changes in color picker user originated
This is not a programmatically initiated event, so it should have the
'userOriginated' property set to 'true'.
- Added test to verify that indeed event is user originated after the change
|
|
|
|
|
|
| |
* Corrected method name TreeDataProvider#getTreeData
The method name was incorrect in the documentation - was showing `getData()` but should be `getTreeData()`.
|
|
|
|
|
|
|
|
|
| |
* Add Test for closing window with focused textfield
verify issue #10642
* Refactor the code about using keyMapper
|
|
|
|
|
| |
Fix https://github.com/vaadin/framework/issues/11268
```buildTime()``` function re-initializes ListBoxes for hours,minutes and seconds values. We need to set correct values in those ListBoxes, before assigning value to the labels displayed instead of those ListBoxes in ReadOnly state, as , otherwise, the selectedItemIndex returns 0.
|
|
|
|
|
| |
Added note that style generator is not applied to the Editor
See also: https://github.com/vaadin/framework/issues/11169
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fixes #10937
- Previously if selected value is null, then index is set to -1; in current implementation if value is null and emptySelection is allowed then set the index to 0. (The position for the empty selection)
- Also, if changing the allowEmptySelection on the fly, ensure, that either index is to-reset to -1 by setting the selected value to null on the client-side (the value before was null) or preserve the value(value was different than empty).
* Change the test case
Since in this pr the behaviour of the NS is changed, therefore old test need to be adjusted.
Change: setting null as value will select empty selection. Before that nothing would be selected and value will be cleared.
Behaviour change in PR: Allow selecting null as value
|
| |
|
| |
|
|
|
|
|
|
| |
* Rebuild calendar pop-up on readOnly state change
Fixes https://github.com/vaadin/framework/issues/6565
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Test case for removing Grid with components
* This reverts commit b2745dc14f17b510df7321ab3f6285ed317da3b3.
Add test case to address the issue with removing gird with components;
Current situation: the grid cannot be removed and client-side throw an error.
fixes: Revert the corresponding change, as it didn't address any issue which was fixed.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- When a TabSheet is scrolled to an end and then resized bigger, more
tabs should appear to the left.
- When a TabSheet is right-aligned in Valo and scrolled to the end, last
tab shouldn't be partially hidden behind the scroller buttons.
- Shouldn't allow attempts to scroll into directions where there is
nothing left to scroll to, even if the current tab isn't fully visible.
Fixes #807
|
|
|
|
|
| |
* Update Release note for RC release
|