| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Change-Id: Ibad2e50d840a2eb0ccb9ac65158e512249a2bc79
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
(cherry picked from commit 24a695b4b7fda581c15600b111d6b6c3459ca1d9)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add new cases for non-same-page navigations, for navigations triggered
from the DOMContentLoaded event handler, for navigations triggered
by user action (clicks), and for navigation rejected by the
acceptNavigationRequest API.
Drop the 'no more signals' waiting time from 10 to 1 seconds.
Task-number: QTBUG-65223
Change-Id: Ic074eaf5aa58f779e31927296ae84d9e4faeaaae
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
|
|
|
|
|
|
|
|
| |
Suppress duplicated progress values coming from chromium.
Verify this behavior reliably (and not only 0 and 100 value) by loading html
with subresources with minor delay through test http server.
Change-Id: Id034dda9012212d54d12fc95d5939ba301577c1c
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
|
Because of the recent problems with unexpected or missing loadStarted
and loadFinished signals (which sometimes interfere with other load's
signals), we add a set of auto-tests for load-signals.
Done-By: Viktor Engelmann <viktor.engelmann@qt.io>
Change-Id: Ia3b65c7b3c4d1ed44e94f409e047db6c6defb821
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|