| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Navigation needs to be done also in doRefresh(..) in similar fashion as in doInit(..)
Fixes https://github.com/vaadin/framework/issues/11416
|
| |
|
|
|
|
| |
* Some formatting changes
|
|
|
|
|
|
|
|
|
| |
* add client side integration for custom styles for checkbox.label and checkbox.input
* add server side integration for checkbox element styling
* add server side tests
* add client side test
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Improve VMenuBar click handling logic
During `updateFromUIDL` inside MenuBarConnector we empty and re-instantiate the components of MenuBar. When we are modifying the Menubar from the BlurEventListener of another component, we ,by this, remove widgets, therefore clickEvent is not fired and the action of the MenuItem is not proceed as a result. (The BlurEvent is fired before the click event in the chain of events. )
To improve the situation, we catch onMouseDown event , which is fired before BlurEvent,by assigning mouseDown flag to true. Then if no click event has yet happened, we delay the execution of update inside `updateFromUIDL` by default 500 ms. Then if click event occurs, it proceeds normally. The time can be increased/decreased using setter.
There is no delay, if we are clicking on the MenuBar as usual or no Blur listener is set.
This change allows setting descriptions
* Remove accidentally committed comment
* Don't update the state on the getDelayMs call
|
|
|
|
| |
* Complete the empty since tag
|
|
|
|
|
|
|
|
|
| |
* Request data update before client response
* fix the accidental commit
* add tests
fixes #11320
|
|
|
|
|
|
|
|
|
| |
* Add missing FocusShortcutListener
Was removed from 8.0 and not readded.
Fixes #8297
* Update Release note for this change
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
* Revert "Update ComboBox internal state on new item added (#11094)"
This reverts commit 56ce91c6160a252ddcd952bca6eb7037120ebf59.
* Add tests to verify the issue
|
|
|
|
| |
* 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
|
|
|
|
|
|
|
|
| |
Fixes #11276
Refactor the code and correct the logic for validation
Rename an internal variable, as it contains more than one type of messages
|
|
|
| |
Fix upload issue
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
|
|
|
|
| |
* Add Test for closing window with focused textfield
verify issue #10642
* Refactor the code about using keyMapper
|
|
|
|
|
| |
Added note that style generator is not applied to the Editor
See also: https://github.com/vaadin/framework/issues/11169
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
|
|
| |
* Suppress unavoidable UIDetachedException
Fixes #11144
|
|
|
|
|
|
| |
* Updated JavaDoc of getColumn(..) method
Fixes https://github.com/vaadin/framework/issues/9920
|
|
|
| |
Javadoc correction of typos in getAcceptMimeTypes() and setAcceptMimeTypes(String acceptMimeTypes)
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
* Changed the way resources, themes, and widgetsets are registered to the HttpService by only using the VaadinResourceTrackerComponent
|
| |
|
|
|
|
| |
Fix handler creation to happen on init
|
|
|
|
|
|
| |
DataProvider (#11167)
Remove objects from DataCommunicator.ActiveDataHandler that are no longer available in used DataProvider.
|
|
|
| |
Fixes #11099
|
| |
|
| |
|
|
|
|
| |
trivial one, fix tests
|
|
|
|
|
|
|
|
|
| |
This allow applications to inject custom default instances when the
current instances cannot be found by regular means.
For example, when VaadinServlet.getCurrent() would return null, a
fallback resolver could be invoked to properly create the servlet and
return it.
|
| |
|
|
|
| |
Fixes #11091
|
| |
|
|
|
| |
Fixes #11083
|
| |
|
| |
|
|
|
| |
Fixes #11002
|
|
|
| |
Fixes #9471
|
| |
|
|
|
| |
Fixes #9997
|
| |
|