summaryrefslogtreecommitdiffstats
path: root/client/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Add explicit handling of ctrl-a (#11693)Tatu Lund2019-08-121-0/+8
| | | | | | | | * Add explicit handling of ctrl-a Fixes https://github.com/vaadin/framework/issues/11678 * Adds test case and formatting the code
* Update Chrome version, snapshots and fix tests (#11684)Zhe Sun2019-08-052-4/+6
|
* Update the since tag (#11675)Zhe Sun2019-07-304-4/+4
| | | | * Update the since tag
* Apply offset to column index depending on presense of selection column (#11667)Tatu Lund2019-07-301-1/+5
| | | | | | | | * 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
* Ensure the upload button has been disabled when set Enabled calling from ↵Zhe Sun2019-07-291-0/+11
| | | | | | | | | succeedL… (#11655) * Ensure the upload button has been disabled when calling from succeedListener with Push enabled * Add Tests to verify
* Ensure that VComboBox.selectedOptionKey gets initial selection. (#11665)Anna Koskinen2019-07-241-2/+9
| | | Fixes #10741
* Improvements to detail row index handling. (#11345)Anna Koskinen2019-07-166-11/+212
| | | | | | - 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.
* 11642 refresh pagelength 0 combobox items after dataprovider update (#11653)Olli Tietäväinen2019-07-121-1/+16
| | | | | | * Fixes #11642. ComboBox with pageLength 0 should be updated if DataProvider changes * added comments, fixed imports
* Ensure the selection has been changed before updating . (#11658)Anna Koskinen2019-07-121-11/+7
| | | | | | | - Initial fix attempt interfered with selection events, added regression testing for those and found a better way to ensure shift selection works on IE11 also with Windows 7. Fixes #11608
* Update release note and Since tag (#11639)Zhe Sun2019-06-271-1/+1
| | | | | | * Update release note for 8.9 * Missing Since
* Adding css class to Editor when on selected row (#11636)Tatu Lund2019-06-261-0/+9
| | | * Adding "v-grid-editor-selected" stylename in editor cell wrapper element when Grid is opened on selected row.
* Clicking on DateField pop-up should select Month/Year (#11531)Anastasia Smirnova2019-06-251-0/+14
| | | | | | | | | * Clicking on DateField pop-up should select Month/Year In Year/Month Resolution DateField should select the value, when user clicks on pop-up Fixes #8447
* Add IE11 workaround for ListSelect multiselection. (#11631)Anna Koskinen2019-06-201-2/+13
| | | Fixes #11608
* Separates a rpc for handling the client event order in DateTimeField (#11574)Zhe Sun2019-06-142-0/+24
| | | | | | | | * Using @Delayed annotation for DateField Rpc * Separate a rpc for handling the time change in DateTimeField * Add test case for wrong event order
* Update Chrome version in Test (#11613)Zhe Sun2019-06-121-2/+4
| | | | | | | | 1) recalculate the offset, as ChromeDriver starts to follow the standard; 2) update screenshots; 3) correct the `click()` call with using coordinates, related to 1) 4) `sendkey()` with using key.modifier adjustment 5) add sleep 6) workaround for mastery failures
* Recalculate the column widths before the first row is added (#11609)Zhe Sun2019-06-061-0/+8
| | | | | | | * Recalculate the column widths before the first row is added Fixes #11607
* Grid Editor: make Tab key skip read-only/disabled fields (#11586)Martin Vysny2019-06-031-25/+86
| | | | | | | | | | | | | | | | * Grid Editor: make Tab key skip read-only/disabled fields Closes #11584 * Extracted DefaultEditorEventHandler.getDeltaFromKeyDownEvent() which allows for easy further Grid Editor customization * Make DefaultEditorEventHandler.Delta public so that getDeltaFromKeyDownEvent() can be overridden * Fixed exception in isEditable() if the widget was not a Field * Refactored DefaultEditorEventHandler.Delta to CursorMoveDelta which expresses the intent more clearly * Merge branch 'master' into master
* Override reserved globals for Firefox (#11598)Artur2019-05-221-0/+872
| | | Fixes #11597
* Fix Grid reordering when there are hidden columnscuong-phan2019-05-201-1/+12
| | | | | | | | * Fix grid column reordering Fix grid column reordering when there are hidden columns and footerRow.join * Add test
* Don't attempt to scroll to the beginning or end if Grid has no rows. (#11570)Anna Koskinen2019-05-201-3/+7
| | | Fixes #11558
* Grid editor: TAB now skips non-editable columns (#11573)Martin Vysny2019-05-161-8/+70
| | | | | | | | | | | * Grid editor: TAB now skips non-editable columns Pressing TAB would shift the focus to non-editable cells when the Grid was in edit mode. This patch makes DefaultEditorEventHandler to skip such columns. Closes #10970 * Add tests
* Add handling for completely empty Grid's column width calculations. (#11569)Anna Koskinen2019-05-141-1/+7
| | | Fixes #11557
* code format (#11555)Sun Zhe2019-05-024-16/+19
|
* Reset Combobox internal state (#11412)Sun Zhe2019-04-242-16/+44
| | | | | | | | | | issue in #11343 and #11385 is not reproducible on top this patch Three different bugs are involved in this fix: we bring the old fix(#11094) back and fixed the other related issues: 1) allow adding the same new item after dataProvider got reset, This is cause by the client side parameter `LastNewItemString`, it saves the value added before resetting. 2) clear the pending newItem eagerly, so that the same value will not be added again.
* Clicking on slider makes handler move (#11519)Anastasia Smirnova2019-04-102-8/+22
| | | | | | | | | | | | | | * Clicking on slider makes handler move Fixes #1496 * Introducing control over clicking behaviour - User will have to enable process of the click event on handle calling `slider.setEnableClickHandler(true);` - Clean-up the handler logic in VSlider.java - Renaming the property to `updateValueOnClick` - Added JavaDocs - Fixing tests
* Fixing autocompletion issue with ComboBox on newer Chrome versions (#11472)Tatu Lund2019-04-101-1/+6
| | | | | | | | | | | | | | | | | | | | | | * Fixing autocompletion issue with ComboBox on newer Chrome versions Newer Chrome versions do not work with random number hack to prevent auto completion, but it finally supports autocomplete=off. * Merge branch 'master' into fix11437 * Merge branch 'master' into fix11437 * Merge branch 'master' into fix11437 * Merge branch 'master' into fix11437 * Merge branch 'master' into fix11437 * Merge branch 'master' into fix11437 * Merge branch 'master' into fix11437 * Merge branch 'master' into fix11437
* Use Enter and Space keys to fire Window header buttons (#11517) (#11534)KatriHaapalinna2019-04-082-5/+32
| | | | | | | | | | * Fixes 11517. Use ENTER and SPACE keys as shortcuts for header buttons * Merge branch 'master' into fix-11517 * Increase sleep time for test failing in validation * Merge branch 'master' into fix-11517
* Read-only combobox should not handle PASTE event (#11529)Anastasia Smirnova2019-04-041-2/+2
| | | Fixes 11528
* setCaption of Panel did not honor setCaptionAsHtml (#11523)Tatu Lund2019-04-022-4/+8
| | | | Verify that correct mode(HTML/TEXT) of caption is set for the Panel Fixes #11521
* Support Firefox 65+ key down event behavior (#11503)Yuriy Artamonov2019-03-292-6/+11
| | | Fixes #11502
* Make improve of caching for hierarchical data optional (#11501)Klaudeta2019-03-211-24/+63
| | | | | Make improve of caching for hierarchical data optional Fixes #11477
* Remove redundant check for for Firefox (#11471)Anastasia Smirnova2019-03-061-10/+1
| | | | | | | | | | | * Add Test file * Remove redundant check for for Firefox It seems that in older versions of Firefox (at least, older than 45) the KeyPress event should be used instead of KeyDownHandler. At some point (works already on 58 version, the current one is 65) the issue was resolved and starting from Firefox 65 this hook prevents from navigating in the pop-up via keyboard. Simply removing additional logic makes navigating in both DateField and InlineDateField possible Fixes #11465
* Ensure pop-up is not opened, when tabbing out fast from Combobox (#11436)Anastasia Smirnova2019-02-251-4/+9
| | | | | | | | | | | Checking that no prior Combobox behavior is broken * Cleaning-up the code Adding UI test * Adding TestBench test
* Fix #11369 (#11403)Maciej Przepióra2019-01-171-0/+17
| | | Clear contents of iframe clone that is in a Window so that when it's reattached to DOM we don't get 404
* Update release note and since tag (#11386)Sun Zhe2018-12-202-8/+12
| | | | * Some formatting changes
* Checkbox allow customizing of input and label classNames. (#11372)Knoobie2018-12-182-3/+58
| | | | | | | | | * 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 (#11356)Anastasia Smirnova2018-12-172-93/+117
| | | | | | | | | | | | | | | * 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
* Prevent IndexOutOfBoundException in VMenuBar.CustomMenuItem (#11285)Jonni Madekivi2018-12-171-0/+1
| | | | | | | | * Fixes #10814 * Add missing tests Fixes #11374
* Move onClick logic to the Connector (#11367)Anastasia Smirnova2018-12-142-24/+25
| | | | | | | | | | * Move onClick logic to the Connector Move onClick event handling from 'VNativeButton' to NativeButtonConnector. Now works as for regular button. Also, adding propagation of the `enabled` value to the state on disableOnClick being true Fixes https://github.com/vaadin/framework/issues/11188
* Apply missing v-readonly style to CheckBoxGroup, when component is readOnly ↵Anastasia Smirnova2018-12-131-1/+14
| | | | | | | | | | | | | | | | (#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
* Complete the empty since tag (#11371)8.7.0.alpha1Sun Zhe2018-12-133-4/+4
| | | | * Complete the empty since tag
* Add more context information to criteriaScript in GridDropTargetConnector ↵vt5122018-12-052-6/+39
| | | | | | | | | | | | | | | | | | | | | (#11321) * Add more context information to criteriaScript in GridDropTargetConnector When using drag and drop in Grids and TreeGrids a criteriaScript can be specified. However, this criteriaScript only gets an event as input parameter. It would be helpful if the criteriaScript would get more information: - the DropLocation - the targetElement which is used as a base for the DropLocation This change provides a protected method in DropTargetExtensionConnector which decides, if the drop is allowed by the criteriaScript. This method is overriden in GridDropTargetConnector to provide the both parameters dropLocation and targetElement. * add Test UI for criteriaScript with targetElement and dropLocation * add some description for the Test UI
* Improvements to updating spacer indexes. (#11353)Anna Koskinen2018-12-051-4/+13
| | | | | | | | * Improvements to updating spacer indexes. - When details rows are moved down, indexes need to be updated from bottom up. Fixes #11352
* Improvement to details row height handling. (#11351)Anna Koskinen2018-12-041-2/+6
| | | | | | - When rows are added, details row heights need to be taken into account in positioning. Fixes #11348
* Revert "Update ComboBox internal state on new item added (#11094)" (#11331)Sun Zhe2018-11-271-25/+10
| | | | | | | | * 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. (#11328)Anna Koskinen2018-11-231-5/+1
| | | | | | * 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. (#11326)Anna Koskinen2018-11-211-1/+10
| | | | | | | | | * 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
* Code formatting (#11278)Sun Zhe2018-11-062-16/+19
|
* Update time in ReadOnly state of DateTimeCalendar (#11269)Anastasia Smirnova2018-10-241-3/+3
| | | | | 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.
* Display the caption of the Empty selection in NativeSelect (#11191)Anastasia Smirnova2018-10-182-1/+29
| | | | | | | | | | | | | | | | * 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