[Webkit-unassigned] [Bug 54206] New: disabling actions in QWebPage

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 10 06:42:02 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=54206

           Summary: disabling actions in QWebPage
           Product: WebKit
           Version: 420+
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Enhancement
          Priority: P2
         Component: History
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: cgorac at gmail.com


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.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list