Bug 54206 - disabling actions in QWebPage
Summary: disabling actions in QWebPage
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: History (show other bugs)
Version: 420+
Hardware: All All
: P2 Enhancement
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 06:42 PST by Crni Gorac
Modified: 2022-07-29 10:47 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Crni Gorac 2011-02-10 06:42:02 PST
It would be good to make it possible to completely disable WebAction-s for QWebPage.

Use case: as an example, I have an application that has most of its functionality coded in Qt, but also has most of the user interface written in HTML/JavaScript, and executing in an instance of QWebView derived widget.  All of the navigation between different HTML pages is handled by JavaScript, however QWebView by default reacts for example to Backspace button, and reloads previous page in the history, which is not desired behavior here.  I tried to disable this in various ways, and best thing I was able to come up with is to catch saveFrameStateRequested signal from page() in my  QWebView derived class, and call history()->clear() on that signal - obviously ugly and incomplete (this signal is fired before actually adding newly loaded page to the history, so I end up always having one item in history, instead of none).  So - it would be useful to be able to control (disable/re-enable) WebActions-s directly from the client code.
Comment 2 Alexey Proskuryakov 2022-07-29 10:47:46 PDT
The Qt port has been removed from WebKit, resolving.