| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Iecd621321fdde29d2d89d910ba46e9dadee58995
|
|
|
|
| |
Change-Id: Ifac318e1e422d39776196fd8f9b4bb670d504578
|
|
|
|
| |
Change-Id: Ib60d6131d36e794bcf72d5f498bb59fafdbf7d0e
|
|
|
|
| |
Change-Id: I8ad89e74b058246939d77165f2d4b5abc3417886
|
|
|
|
|
|
| |
It appears that iOS6 will not make new request (at least for images) to a server to which there is already a connection open which possibly will be kept alive after the current request is done (Connection: Keep-alive asked by the client and not denied by the server)
Change-Id: If4e6233457fced3760a931b7953fa1713fee3452
|
|
|
|
| |
Change-Id: Id0d82eabab63681b9d01c0312588fdfe1659860f
|
|
|
|
|
|
|
|
|
| |
When ProgressBar was split out from ProgressIndicator,
ProgressIndicatorConnector was accidentally left inheriting the
VProgressBar widget from ProgressBarConnector instead of using its own
VProgressIndicator.
Change-Id: Ie7c5d3b68af871d5eb2a86f3d720af3b23048793
|
|
|
|
| |
Change-Id: I3d773640d2f1c8cd1b71c673685afd7059811d16
|
|
|
|
| |
Change-Id: Id9eaee65762b0dadd59f3e730d3ff11712ab87fe
|
|
|
|
| |
Change-Id: Ic834ddabdeeb2a9cc453b67e5202ff1aab44dffd
|
|
|
|
|
|
| |
The locale data is now tracked per UI instance and no longer sent in every request.
Change-Id: I4bebd00327da6f8d812181fd76a85eb6196d0010
|
|
|
|
|
|
| |
SMARTSPRITES-36 (#9959)
Change-Id: Ibf549acba14a8b884424a5e2c98f3a4aac5de84c
|
|
|
|
| |
Change-Id: Ibcabe18581e4ad021ad1b58919c77fd97f2ad47c
|
|
|
|
| |
Change-Id: Ie72e1a3ab72be00c99548a740f16721fb7edab00
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the server happens to update the state of the RTA while a user is
typing then the users text will be replaced by the value on the server. To fix
this the RTA should not update if the value is the same as the one
cached on the client side.
Also moves blur handling and server<->client syncronization to the
connector.
Change-Id: Ia807b1e2aa210eb881e4b9cea0870c0c5a9254b2
|
|
|
|
| |
Change-Id: I91489d73bec165b5e755b5d76bf220043bee0d66
|
|
|
|
| |
Change-Id: I52cbd9582345a3c0d49caf2ad265a659bf3fe0f1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The deadlock check in accessSynchronously() was triggered in cases where
one session was locked and tryLock() in access() did manage to lock
another session and thus attempted to run the runnable right away.
runPendingAccessTasks() needed accessSynchronously() just for setting up
the current session instance - the session was already locked and
cleaning up the CurrentInstance values afterwards was not needed. Just
setting the current session without accessSynchronously() gets rid of
the inappropriate deadlock detection as well as some overhead with
managing locks and CurrentInstance values.
Change-Id: Ib956d68884d6703dce2633a455c4857bb06651af
|
|
|
|
| |
Change-Id: Ic270e5c0aa1b28947b735fcb258bc9629d53cc21
|
|
|
|
| |
Change-Id: I05f88e398e7e28f476d8c0d50b7f9ac54a7cba0b
|
|
|
|
| |
Change-Id: Ibbe209a6a67e594318a7ac50f962c48aeab4730d
|
|
|
|
|
|
|
|
| |
Vaadin 7.1 (#10217)
Originally fixed as #10189.
Change-Id: I0fe6fbb2452bcdb75fed4ea9ef92ea7b739cbb22
|
|
|
|
|
|
|
|
| |
* access is run right away instead of the next time there's a request
from the server.
* Non-inheritable CurrentInstance values are not carried over to access
Change-Id: I6a9f3f2a74647357fe02c43e96878d803cfaf207
|
|
|
|
| |
Change-Id: Ic7389a06726026383b96de80b0d038ed11e9d273
|
|
|
|
| |
Change-Id: I7ca62c5706fd37e7c44ed46703bcdce159b367f4
|
|
|
|
| |
Change-Id: I70d7d78a0d9de76080f6e0770a48504af8abdd84
|
|
|
|
| |
Change-Id: Icfaa8f97824d8ed92eaee786cee8c92083dc1084
|
|
|
|
| |
Change-Id: Iadf8831b01a292d5e29fea26c877541ab4dc5919
|
|
|
|
|
|
|
| |
Vaadin 7.0 disabled rendering of tabs that are not shown, but the place
holder mechanism was still retained. Now it is removed.
Change-Id: Ic15b7f56852816d73916ef78f5997eb5e40f9cab
|
|
|
|
| |
Change-Id: If162e81a29bbc982857e2a165a983e161ea837ee
|
|
|
|
|
|
| |
Serializable
Change-Id: I197b2d62282ee957458e05d9cac357df47f05e85
|
|
|
|
| |
Change-Id: I83d8c96a6877ea33b270a1a4a2c6f360a8147518
|
|
|
|
| |
Change-Id: I7516be18401640ded3eb6174b5375bb452a2ba00
|
|
|
|
| |
Change-Id: Iaeef438de48ef9bda33fb81b0bb7f71d134b17ca
|
|
|
|
|
|
| |
using the debug window
Change-Id: I3b5a8ac4f33c7e8828e34c46056b8ecd6c05a436
|
|
|
|
| |
Change-Id: Iaefdebfb24bedff95239ea8813b29723b3437f5b
|
|
|
|
|
|
| |
view (#11722)
Change-Id: Ifab9aa0021bde58280fd75370e5df46fb5efa7a7
|
|
|
|
| |
Change-Id: Ice20a168dd8c0dc14f8e4600f24e2b788cb38bc4
|
|
|
|
| |
Change-Id: I6b9fb8a664974b68b35050a40ba19bce440b6b3c
|
|
|
|
| |
Change-Id: I1c98c353314197047265d26a0464ab7cc9c79520
|
|
|
|
| |
Change-Id: I7f5736fd456c21878a0eabdbff46a648932d3516
|
|
|
|
|
|
|
|
|
|
| |
converter is needed (#11863)
The previous logic had two flaws
* It allowed converter model type to be a sub type of the model type but not vice versa. Similarly for presentation type.
* If the user has set a converter it should be used and not be replaced unless it is absolutely sure that it cannot in any possible way handle conversion (e.g. converter from integer to double cannot handle string to list conversion). If there is a slight chance that it can handle conversion, let it be and let the user set another converter when needed.
Change-Id: I2e1c0b3aac90be63ddbc780195f8428398e28ada
|
|
|
|
| |
Change-Id: I523140051e1034b5fab501517e70209f29b6b869
|
|
|
|
| |
Change-Id: I53e413f8e9c8754915d80c30d3dca97eb1881c74
|
|
|
|
| |
Change-Id: I46a2622585ed69a1db4c6abf4aca4387387a0f97
|
|
|
|
| |
Change-Id: I8f04cc0ddc034ce7cb43cc7f6646ddffcba64a4b
|
|
|
|
| |
Change-Id: If8c4a5d9ff470703943f6f6f9cd599ecd1d4be49
|
|
|
|
| |
Change-Id: Ie9281ff5e9805be89942bf3ca8259740f49e15ab
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement VaadinPortlet.getCurrent() to use VaadinService.getCurrent()
instead of having a separate thread local variable. This is done to
avoid classloading issues when determining which instances to preserve
in CurrentInstance.setThreadLocals. The two current instances have
previously been kept in sync in all cases except during
VaadinPortlet.init where VaadinService has not yet been created.
VaadinPortlet.setCurrent() is removed as no way of preserving its
semantics has been found. This breaks API compatibility, but is probably
better than having a deprecated implementation that can not work as
expected in all situations.
The same changes have also been made to VaadinServlet to maintain the
symmetry.
Change-Id: I0a1ccc07a4aeecec558a9aaae211bd56207313d8
|
|
|
|
|
|
|
|
|
|
| |
Used with TrackMessageSizeInterceptor and with client-to-server Websocket message splitting (see #11648)
The original issue that the delimiter can not appear in the message (unescaped) is apparently fixed in Atmosphere 1.0.13
Also ensure the max size of a websocket fragment in bytes does not exceed the buffer size (#11842)
Change-Id: I768524bb54a5b8b9479dc7bda821256bd843dc52
|