| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Sometimes Chrome reports 1ms for very short times to thwart
timing attacks, and sometimes Firefox seems to report 0ms. Make
the test accept these special cases.
Add support for PhantomJS 2 which does support high res time.
|
|
|
|
|
|
|
|
|
|
| |
Due to action key generation on ActionManager a wrong action
may be executed if the component that fired the wanted action
is already detached.
This patch makes action keys globally unique, simplifying the
approach of #8495 but reusing its tests.
Fixes #5864
|
|
|
| |
Requested feature: allow setting DateField to a certain starting point without selecting a value.
|
| |
|
|
|
| |
Paragraph about existing `styles.css` file needed a bit of rephrasing.
|
|
|
|
| |
Remove Chrome Frame specific part of X-UA-Compatible but keep the
meta tag to override compatibility mode settings where applicable.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Picked from #9551 in 7.7
There's an intermittently happening issue with both Table and TreeTable,
which results in row data disappearing.
This change removes a method which is probably a vestigial one from over
five years ago and other changes are handling the things the method used
to perform. Currently the method removes rows deemed unnecessary from
the row buffer. The problem is, those rows are visible to the user and
removing causes row contents to be lost.
Also included are manually runnable test cases which demonstrate that
this removal actually prevents the issue from happening.
Fixes #7964
Fixes #5030
|
|
|
|
|
| |
by calling calendar.setTime(today);
after rollAmount has been initialized and given a value, we can reset the calendar's internal time back to the correct date. As it is currently implemented; calling calendar.getTime() will result in a wrong date, it returns the first of the month with the correct time.
The function addInitialEvents() is called AFTER the calendar's time has been subtracted from (by calculating the rollAmount), as such this results in an incorrect internal time and the 'Day' button does not switch to the correct day. Instead it shows the first of the month here too.
|
|
|
| |
Fixes #9788
|
|
|
|
|
|
|
| |
Picked from #9161
Fixes #7261
Fixes #5178
Fixes #4409
|
|
|
|
|
|
|
|
| |
The fix allows both column-reorder handler and column-sort handlers to run
in parallel; on touchend it is decided whether we will perform sort or
reodering. This will enable user to sort on touch screens even with column
reordering enabled.
Fixes #8632
|
| |
|
|
|
| |
As per suggestion of Fredrik Rönnlund following https://dzone.com/articles/working-vaadin-with-scala
|
|
|
| |
Fixes #8292
|
|
|
| |
Resolves #9760
|
|
|
|
| |
Chrome 55 and later cause extra scrollbars on the testing cluster but
not in local tests, probably due to a rounding error in the browser.
|
|
|
| |
Add support for stable 8.1.x releases.
|
| |
|
|
|
|
|
| |
IE10-11 have a related bug
https://connect.microsoft.com/IE/feedback/details/811408
that is only fixed in Edge.
|
| |
|
|
|
|
| |
Otherwise, TabSheet close button may break the small theme
in ReindeerThemeTest when the caption width is rounded down.
|
|
|
|
|
|
| |
The test works on Firefox under low load, but not when
the browser VM is slow due to load, in which case Firefox
sometimes executes scripts out of order. This seems to be
due to a Firefox bug - the generated HTML looks correct.
|
| |
|
| |
|
|
|
| |
Fixes #9628
|
| |
|
|
|
|
|
| |
Fixes #9518
Fixes #8991
Fixes #8687
|
|
|
|
|
|
|
| |
This patch provides a simple fix for the majority of issues. There are still issues that should be fixes by refactoring parts of the logic in AbstractSingleSelect.
This patch does not unify the handling of empty values in the TestBench elements of various AbstractSingleSelects.
Fixes #9494
|
|
|
| |
Karaf is now tested by a separate module.
|
| |
|
| |
|
|
|
| |
This feature was present in Vaadin 7 but missing from Vaadin 8
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Fixes #9550
|
| |
|
| |
|
|
|
| |
Fixes #9703
|
| |
|
|
|
| |
Fixes #9653
|
|
|
| |
Fixes #9705
|
|
|
| |
Resolves #9191
|
|
|
| |
It says ConfigurableDataProvider, but there isn't a ConfigurableDataProvider class.
|
|
|
| |
Remove pre-release mention and update current browser versions.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As there is no "request end" call after invoking UI.access() from a background thread,
the connector map was not earlier properly cleaned afterwards. If you toggled visibility of a
component from the background thread, the tracker state became inconsistent.
If this becomes a performance problem, it could probably be optimized to that cleanup
is done in request end and only at the end of access if not inside a request.
Fixes #9654
|