| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I6f16b9c55f661f5f75628ff627a01f8ec35e714e
|
|
|
|
| |
Change-Id: I1b473b9f5316674c5c5ed9a35d776fb8906eb559
|
|
|
|
| |
Change-Id: I56ee44f34307d76c8c98ca3346feed8e7ee2f72e
|
|
|
|
| |
Change-Id: Id55ad5ed620bd5c187b70ae2a2d0a4c4adea382a
|
|
|
|
| |
Change-Id: I2a25b4149f927ee7940edf596e8cebaaa48dcd0d
|
|
|
|
|
|
| |
Added -1 check and test.
Change-Id: I3f6c61417353884d22d8e6b33ef21319475c1907
|
|
|
|
|
|
|
|
| |
Some changes in BasicBackwardHandler and BasicForwardHandler.
Also test was added (CalendarBackwardForwardTest).
Changes after review.
Change-Id: Ibe0283534b784e3c18134619e1843440ca74e65c
|
|
|
|
| |
Change-Id: Idc51aa5ab97a9d3f7a1f316d9536ae1cbaeafe38
|
|
|
|
|
|
|
|
|
|
|
|
| |
At this moment behavior of restoring scroll position more like as in
7.2.6. But restoring is only in case of removeAll() - addAll() (or add()
one time - then restore index is reset).
In 7.2.6 restoring of scroll position was the result of client defect
(scrolling in lazyScroller was not changed if variable "firstvisible"
fromserver was 0). This "defect" was fixed in one of the patches.
Change-Id: I2e2fb8749ec95f3409caeacafff46c4c29159e74
|
|
|
|
|
|
|
|
|
|
| |
Fix: if to remove (container.removeAllItems()) and then to re-add(container.addAll(..)) the same collection in table container - > scroll position is not loosed now.
The hash code and scroll position of the old container is stored when a new container is added.
If the new container has the same hash code, we restore the scroll position.
The scroll position is not restored if another items added to the container.
Change-Id: I52a22c3c1c7b71f1b3447b9d592ab8fececd67b8
|
|
|
|
| |
Change-Id: I74bea857306fac5123aa86cdabc70d81c2a72094
|
|
|
|
| |
Change-Id: Ic44e8abf1e7405735c940573558e150b4e0de35d
|
|
|
|
| |
Change-Id: I8d5580895a218440a8295ed79453d6cbe24195b1
|
|
|
|
| |
Change-Id: I8b72b362134d564165a7037e0722c3ff28f59497
|
|
|
|
| |
Change-Id: Ie239bf110909f8acb47f2141431965061f9ac407
|
|
|
|
| |
Change-Id: Ib7ef769b7537675c681ac1fab24a425d19a267e7
|
|
|
|
| |
Change-Id: I7b3556d5f9c1dd84beec638d7fbff1c5382070a4
|
|
|
|
|
|
| |
Added null check and corresponding test.
Change-Id: I197dad14d6b5f7bf9bedcdf083d4b1f0f20efdcd
|
|
|
|
| |
Change-Id: Ia7dd54c4cf10a2c56a5ef36864a6bb94f1d9167f
|
|
|
|
| |
Change-Id: I3b527084d23ee8bd49887bef3d018c1003f492e2
|
|
|
|
| |
Change-Id: I0b5976abf0d8804e8cd34c5dd489da8617ef89f1
|
|
|
|
| |
Change-Id: I1a8a895d631889e04f7acbde29306e86da344a23
|
|
|
|
|
|
| |
Added proposed fix
Change-Id: I88085546c2bf47f1e0952d64efadfc40bac12987
|
|
|
|
|
|
| |
VaadinService.fireSessionDestroy: session.accessSynchronously -> session.access
Change-Id: I72e08c9285e6b34dac54401c6c84b7175133e481
|
|
|
|
| |
Change-Id: Ia4c212ead39d7b71c56db586c0a8559935cae263
|
|
|
|
| |
Change-Id: Ie801a17ed1eff29a7dc6be61755241777071ab8f
|
|
|
|
| |
Change-Id: I2440f6471b8bbb016497bf59cffd023b013460dd
|
|
|
|
| |
Change-Id: Iccf6a2b0da6e47b5b14c40e0ebaab52df1eef92a
|
|
|
|
| |
Change-Id: I663b39a37bcdf4383fa76d04acd127503ced11df
|
|
|
|
| |
Change-Id: Ia746e41b7dd81b3465895aad4ca39991aac17d89
|
|
|
|
| |
Change-Id: Ia279c4da78ca04e0d3727b605e2ce68b99e8cd65
|
|
|
|
| |
Change-Id: I114ea5bf9d55c78826c1163206caf585b96143ef
|
|
|
|
|
|
| |
Comparisons with the ==-operator between a proxy and it's underlying
instance fail, so we should use a custom equals method instead.
Change-Id: Iaa86ae830fecbedfb1f55636e25f5affebf5aba3
|
|
|
|
|
|
|
|
| |
New version of vaadin atmosphere, picked change from main codebase:
https://github.com/Atmosphere/atmosphere/commit/9eeb5768
Tested manually against Jetty 9.2.3
Change-Id: I90f4a90b1ff651cc475eb01c2156d3c58abd8c2c
|
|
|
|
|
|
|
|
| |
When the UI had an invalid string the ValueChange event was fired
before setting all the flags causing an invalid isValid result when
handling ValueChange. Now the event is fired after the flags are set.
Change-Id: Ie4e6ba21edc81bf41c2c661aa27e0ace71e1bef0
|
|
|
|
| |
Change-Id: I90ec428ae11727b9762d53ebb8d94f8c850c425b
|
|
|
|
| |
Change-Id: I68a629a29cc0d6efd2dd7788875a1dc4182ee6bf
|
|
|
|
| |
Change-Id: Ifcfe1f90b795072c12d3118db33f3df6c96c568b
|
|
|
|
| |
Change-Id: I235ebe6250b9c03bbea393df7e8eb8823d119a2c
|
|
|
|
| |
Change-Id: I82e3caef915b6a8683608f1834130468b3f16dbf
|
|
|
|
| |
Change-Id: Id3829562f7bb898ee0df873de90f0339ad06adff
|
|
|
|
|
|
|
|
| |
This reverts the new default behavior introduced in fix for #8855.
If you want empty rows/columns to be ignored when rendering,
use GridLayout.setHideEmptyRowsAndColumns(true)
Change-Id: I38a8717d79cec7739b649174654b615db9d8dc7e
|
|
|
|
|
|
|
|
|
|
| |
As described by Johannes, the RPCRequest constructor first takes whole
JSON as string and builds its attribute json from it (by parsing).
Then it reads from this parsed JSON the array called "rpc".
However it previously did a .toString on it only to re-parse it.
Newer json versions complain that "rpc" is not a string, but an array.
Change-Id: If4bb45abad551b183d757f0aa326c37c070ce103
|
|
|
|
|
|
|
|
|
| |
drag image (#13836)
Amend : Fixes the comments for the last commit.
Amend 2: Fixes a nullpointer found in a certain test scenario
Change-Id: I72327f5f8ab9e46d88e1ebed8f1db3a7da39d7d8
|
|
|
|
|
|
|
|
|
| |
Makes any Label text colored, by default the same as $v-selection-color.
Modify the Forms and Labels examples to use the new style, and remove
the fixed color from “light” style form layout for header labels.
Change-Id: I27a4fce56b1f734aa5c2c837bf1684284b0d96cc
|
|
|
|
|
|
|
| |
Available as additional style names for buttons, text fields/text
areas, combo boxes, date fields and labels.
Change-Id: I12f36935a690f5bf3f12333f5bd4ac986d4efd1f
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the font icon to version 4.1.0.
The enum is now sorted alphabetically by the icon name, while
previously it was sorted by the code point.
The new list is copied from http://fontawesome.io/cheatsheet/ which
contains all the icons in the font.
Change-Id: I41a69248a9e3bd25c90b7f79b5814cdb46b10bbc
|
|
|
|
|
|
|
| |
All HTTP request based push request invoke onRequestStart/End in the servlet.
We need to trigger start/end separately in push handler only for websocket messages
Change-Id: I16064ea88b0c70812f247028ddb23560536db70d
|
|
|
|
| |
Change-Id: I079492e8a2f3d37d44de3213a2dffb746f726079
|
|
|
|
|
|
| |
The previous patch caused TestCurrentPageFirstItem to fail.
Change-Id: I6eec8818f5ba2ce847a696afa40ba423ec482668
|