| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ie7936fd2eaca0e0c5da1f6ed8f12238ae207b7eb
|
|
|
|
| |
Change-Id: Ib1211a7a2282753b329129615a544264e62d1ed5
|
|
|
|
|
|
| |
Rewrote event selection.
Change-Id: I8f0dd1c5ec736ea14037619b1656a79b7e3532be
|
|
|
|
|
|
| |
(#15355)
Change-Id: I04a91349fce452aa26c304413061440ad74465cc
|
|
|
|
|
|
|
|
| |
This prevents chunked-transfer mode and allows server infrastructure to
decide correctly on things like compression which benefits from knowing
a content length.
Change-Id: I4e969e0874b506d0f61526662ee78418987937c4
|
|
|
|
|
|
| |
This patch makes commit() work properly if an item was modified and later deleted.
Change-Id: I5a00024112e7b6bb7ab3750c292a872937f03af9
|
|
|
|
| |
Change-Id: I2ab2d24ec05bb618969f59ea15d3a971f88009ca
|
|
|
|
| |
Change-Id: Ib7fd42e6017d0b78e6d5e6bd7f531f0cd6c8c0ab
|
|
|
|
| |
Change-Id: Ieaed329ed85c68d0da8bd169b4cc5c5886dde212
|
|
|
|
|
|
|
|
|
|
| |
Usually first a resource is served with the lower code block. this
provides cache-control, expires and last-modification headers to the
browser. But when a not-modified response was served, these headers
were missing. This effectively caused the caching to no longer work once
the not-modified responses are sent out.
Change-Id: I9b1f0cacc91734f88bb0384872da0d426d4b5fe0
|
|
|
|
| |
Change-Id: I476d8c7e53ce90941b00deefffc1b6a7ea63b43b
|
|
|
|
| |
Change-Id: I1e3783d21cb5f2832838dfe36c91c7f6a4ddb313
|
|
|
|
| |
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: I4761ab889bfacedd66bd7ed5f37fe763d7539bef
|
|
|
|
| |
Change-Id: Iae1723bfcfa56084a1339247b1f82e9277555a5e
|
|
|
|
| |
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
|