- Based on TB4 Parallel testing.
- Browser setup no longer uses static capabilities.
- Some code cleanup here and there.
Change-Id: I5c419316cd36f4f5041eaa8da8fda3d8b46596c4
Tooltips are no longer removed but moved outside the viewport,
which broke several tests.
Rewrite related tests using TB4 to be stable across all
browsers. There are differences between browsers (e.g.
position -999 or -1000, gwt-uid-* varied between browsers
etc.) so TB2 tests kept failing on some or all browsers.
Some tests have been renamed to better indicate what they
do.
Change-Id: Ia7276871f3c26d506dc70e1719347d020b547bfc
Fix for 'Aborting layout after 100 passess' (#13359)
'Aborting layout after 100 passes.' is caused by LayoutManager falling
into a loop on rounding fractional layout slot sizes up and down while
trying to fit layout's content in the space available. LayoutManager
round always up, that causes this issue with IE9+ and Chrome. This
change helps LayoutManager to round fractional sizes down for browsers
that causes problems if rounded up.
Browsers may fall into the loop especially with a zoom level other than
100%. Not with any zoom level though. Problematic zoom level varies by
browser. OrderedLayoutExpandTest uses zoom levels other than 100%. Test
for Chrome is the only one that really is able to reproduce error
without the fix. IE9/10 would too, but the zoom level could not be set
exactly to the required 95% for IE. Test works best as a regression test
for other browsers.
Change-Id: Ie840b074df5fed5ea3b15fba9a6fd372a5c0b76a
The test was always failing since it relied on the GWT generated gwt-X
ids in its locator. Converted test to TB3 and used a different approach
for testing the same thing.
Change-Id: Ib806086c19b58fa9fac16e2270c46830f0706b22
Update TB3+ convention to use a separate *Test file
For any issue there should be a UI class, e.g. LabelSomething and a
Test class which has the name of the UI + Test, e.g. LabelSomethingTest.
The LabelSomethingTest contains ALL tests which depend on LabelSomething
and are named accordingly to what they test.
For special and legacy cases also LegacyApplication and UIProvider are
supported in addition to UI classes
Change-Id: Ifc0180b377284bbd029202494ad194d324f8213b
Removed some obsolete (hopefully!?) code doing some odd things with caption height calculation and some refactoring to make that part of code slightly more readable.
Change-Id: I960e4a9eba0388281868f18a182c8788cedf08f9
* Always use expansion logic if the layout's size is fixed
* Ensure e.g. expansion changes happen even if no hierarchy or
measurement changes (#10161)
* Separate the calculation of expand ratios from the adjustment for the
sizes of children without expansion
* Ensure there are element resize listeners for all elements that should
be measured (#10488)
* Postpone calculations if there are elements that have not yet been
measured
* Use measurements for fixing the height under more circumstances
* Only update based on hierarchy & state if something might have changed
Change-Id: I8542afbcb7e93d44bd0dff751a56ed10033937fc
Teemu Suo-Anttila
Artur Signell
Juuso Valli
Sauli Tähkäpää
Henri Sara
Tomi Virtanen
Juho Nurminen
John Ahlroos
Matti Tahvonen
Leif Åstrand
denisanisimov
Johannes Dahlström