Details
-
Suggestion
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
None
Description
I've been thinking about some improvements for QWebEnginePage::findText to make it more powerful than QtWebKit's equivalent.
Features I'd like to see:
- A way to get the positions of all matches, to present the user with a list of matches, and the index of the currently selected match.
- An equivalent to QWebPage::FindWrapsAroundDocument and maybe the other QWebPage::FindFlags (though I don't need the others myself)
- The ability to search for a regex on the page instead of a fixed text
- A flag to start (or continue) the search at the position the page is scrolled to, rather than the top or the next match.
I have no idea how feasible those would be, which is why I decided to open a single bug for them for now, to discuss what makes sense and what doesn't.
Attachments
Issue Links
- depends on
-
QTBUG-74588 Replace QWebEngineCallback with std::function
- Closed
- relates to
-
QTBUG-63235 Qt WebEngine Changes in Qt 6
- Closed
-
QTBUG-80858 Consider controller like approach for findText() workflow
- Reported
-
QTBUG-80857 Expose text query in QWebEngineFindTextResult
- Reported
-
QTBUG-69736 Add FindFlag to only search at start of words
- Closed