Bug 38622 - QGraphicsWebView and QWebView does not send QEvent::RequestSoftwareInputPanel when it gets the focusIn event.
Summary: QGraphicsWebView and QWebView does not send QEvent::RequestSoftwareInputPanel...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Qt (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt, QtTriaged
Depends on:
Blocks:
 
Reported: 2010-05-05 18:47 PDT by Manish
Modified: 2014-02-03 03:50 PST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manish 2010-05-05 18:47:38 PDT
This feature will enable the launching of virtual keypad as soon as QGraphicsWebView and QWebView gets the focus and the focused item is a editing field. Can be useful in below cases:-
1) Lets say we are in an application with input software panel (virtual keyboard) launched and we are editing something. While editing something i switched to some other application and after a while i switch back to the previous application (where virtual keyboard was launced), what i expect is virtual keyboard launches back. But it is not happening since QEvent::RequestSoftwareInputPanel is not sent by QGraphicsWebView and QWebView in focusIn event.

2) setting focus programmatically (QGraphicsWebView::setFocus QWebView::setFocus ) should send QEvent::RequestSoftwareInputPanel if the focused item inside the web page is an editing field.

I think this is a important to have for better expereince.
Comment 1 Jenya Brodskaia 2010-11-09 10:38:32 PST
I am not sure we need to do it this way. Some webpages have focus on the editing field from start. For example - google.com. We do not want virtual keyboard to come up by default every time we open such page.
Comment 2 Jocelyn Turcotte 2014-02-03 03:50:42 PST
=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.