| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
| |
Keep the ComboBox popup at the same position relative to the ComboBox
when the view is scrolled.
Fixes #5043
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
When child components are removed from a
VerticalLayout/HorizontalLayout, do not remove other children from the
DOM if no other hierarchy changes are made.
Fixes #7713
|
| | |
|
| |
|
|
|
|
| |
When child components are removed from a CssLayout, do not remove other
children from the DOM if no other hierarchy changes are made.
Fixes #7712
|
| |
|
|
|
| |
Added utility constructor for Button(Icon, ClickActionListener):
new Button(VaadinIcons.AIRPLANE, e -> { ... });
|
| | |
|
| |
|
| |
Fixes #7341
|
| |
|
| |
Fixes #9803
|
| |
|
| |
Fixes #9832
|
| |
|
| |
The test testReuseTextFieldOnScroll() often crashes PhantomJS 1.
|
| |
|
| |
Fixes #9152
|
| |
|
|
|
|
|
|
|
| |
Icon load detection code does not handle error events so broken images
will cause tests to fail forever. In other cases also, it seems very
rare to need icons to be loaded before interacting with a combo box. If
there really are use cases for this, it would be better to have a method
to query if all icons are loaded so that special tests can use this method.
Fixes https://github.com/vaadin/testbench/issues/916
|
| |
|
| |
Fixes #9425
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
IE10-11 have a related bug
https://connect.microsoft.com/IE/feedback/details/811408
that is only fixed in Edge.
|
| | |
|
| |
|
|
|
|
| |
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
|
| | |
|
| |
|
| |
Fixes #9550
|
| |
|
| |
Fixes #9653
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
Closes #9694
|
| | |
|
| |
|
| |
Fixes #9170
|
| |
|
| |
Fixes #9686
|
| |
|
| |
Fixes #9637
|
| | |
|
| |
|
| |
Fixes #9071
|
| |
|
|
|
| |
Fixes #9606
Fixes #9645
Fixes #9647
|
| |
|
|
|
| |
drop (#9605)
Fixes #9600
|
| |
|
| |
Fixes #9596
|
| |
|
| |
This also fixes/improves AbstractDateField validation.
|
| |
|
| |
Resolves #9372
|
| |
|
|
|
|
| |
This patch changes Grid Columns, so they can have different value and presentation types. A presentation provider can be given when setting the renderer for a column. This provider takes the value of the column on a row and chooses what to present for this value. Using this approach it is easier to have an editor for the actual backing data instead of the presentation of it.
Fixes #8656
Resolves #9588
|
