summaryrefslogtreecommitdiffstats
path: root/tests/auto/widgets/spellchecking
Commit message (Collapse)AuthorAgeFilesLines
* Various clean-ups around QWebEngineViewPeter Varga2021-07-131-2/+3
| | | | | | Pick-to: 6.2 Change-Id: I16f27054871f63526946101e07cb0dcf4aa3b390 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Add spellchecker support and qwebengine_covert_dict to cmakeMichal Klocek2021-06-142-2/+51
| | | | | | | | | Add spellchecker dictionary conversion tool. Change scope of gn object imported variables to function scope. Pick-to: 6.2 Change-Id: Ice579a89e20b80034b675e7f767a774100478472 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Move QWebEnginePage to coreMichal Klocek2020-11-241-1/+1
| | | | | | | | | [ChangeLog] QWebEnginePage is in QtWebEngineCore Task-number: QTBUG-74585 Change-Id: Id326c89c868e9e7d53488bbd12cb321e1a0b79b7 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
* Move profile from widgets to coreMichal Klocek2020-11-201-1/+1
| | | | | | | | This just moves class to core. Task-nmuber: QTBUG-74585 Change-Id: Id046eee21043f086f5f45727bc3ce7c965695b7c Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Merge all webenginecontextmenudata wrappers into one classMichal Klocek2020-08-121-12/+8
| | | | | | | | | | | | | | | | | | | | | | Introduce new class qwebenginecontextmenurequest in core which merges: * qquickwebenginecontextmenurequest * qwebenginecontextmenudata * implictly shared webenginecontextdata Unfortunately new class has to be QObject, since we want to reuse it qml. Q_GADGET can be used only as a value type, however we need to know if request is accepted or not in qml, therefore it must be passed as pointer. Since we use QObject now, class is no longer implicitly shared, however we only allocate request once and reuse the object for every new request (it is still copied in qml just to keep it aligned with other request handlers) [ChangleLog] QWebEngineContextMenuRequest is replacement for QWebEngineContextMenuData Change-Id: Ib387ec2065361a4bacc20675ca7352ab75a0e436 Reviewed-by: Michael Brüning <michael.bruning@qt.io>
* Move QMenu handling from page to viewMichal Klocek2020-08-121-1/+1
| | | | | | | | [ChangeLog] createStandardContextMenu is moved from QWebEnginePage to QWebEngineView Change-Id: I08a7a1f7e55ca7396547006523cdec250a3ad117 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix QFlags warningsAllan Sandfeld Jensen2020-01-171-4/+4
| | | | | Change-Id: I2938d5a44df01c7d9c70e18ecc293fc91079e5bd Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Merge remote-tracking branch 'origin/5.13' into devAllan Sandfeld Jensen2019-07-241-8/+35
|\ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/3rdparty src/core/core_chromium.pri tests/auto/quick/qmltests/BLACKLIST tests/auto/quick/qquickwebengineview/BLACKLIST tests/auto/widgets/qwebenginepage/BLACKLIST tests/auto/widgets/qwebenginepage/tst_qwebenginepage.cpp tests/auto/widgets/qwebengineview/BLACKLIST Change-Id: I11b26f5eebde29c4c62247b90e11e3ae40789fe4
| * Fix spellcheck test flaky failure with misspelled word missingKirill Burtsev2019-07-121-8/+35
| | | | | | | | | | | | | | | | | | Work is done asynchronously by chromium SpellChecker object. Therefore there is no guarantee that on ShowContextMenu event for WebContents there will be a result with misspelled word. Change-Id: I2978ed99e4c14f0a7d9086853c5218f82ea1ab60 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* | Ignore persisted spellchecking preferencesJüri Valdmann2019-07-151-35/+48
|/ | | | | | | | | | | | | | | | | | | | | | Ignore on-disk values of spellCheckEnabled and spellCheckLanguages prefs to preserve backwards compatibility. Fixes deterministic failure in second run of tst_spellchecking because the first run disabled spellchecking. Put all settings-related tests in tst_spellchecking into one test and pretend to check that settings are not persisted. Since settings are currently read and written on independent task sequences without guaranteed ordering, the test would succeed even if settings were persisted. Specifically, in code like this profile = new QWebEngineProfile("MyProf"); // 1 delete profile; // 2 profile = new QWebEngineProfile("MyProf"); // 3 the write from line 2 will usually happen after the read from line 3. Once persistence becomes a public feature we probably should add some way to guarantee the proper ordering of reads and writes. Change-Id: Icb2290417049848dbe68b7f991bbe2d52756f295 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Clean-up of test namesAllan Sandfeld Jensen2018-07-238-0/+309
We want to only use the qwebengine-prefix for tests of actual classes. Change-Id: I0ab4e17f3b4994cc67e836112965307236d61549 Reviewed-by: Kai Koehne <kai.koehne@qt.io>