From 4da1db8fb60b444dc112b41804a3ac7480197bd2 Mon Sep 17 00:00:00 2001
From: Pierre Rossi <pierre.rossi@digia.com>
Date: Fri, 11 Apr 2014 18:46:40 +0200
Subject: Add a way of using UI dialogs for authorization

We could use this to prompt the user for various feature permissions
that we are not ready to expose in our API.

Change-Id: If6e6a16aca4142b0564121dfc7677b7c4996f742
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
---
 src/webenginewidgets/api/qwebenginepage.cpp | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'src/webenginewidgets/api/qwebenginepage.cpp')

diff --git a/src/webenginewidgets/api/qwebenginepage.cpp b/src/webenginewidgets/api/qwebenginepage.cpp
index 6fcababbf..ec0c0224d 100644
--- a/src/webenginewidgets/api/qwebenginepage.cpp
+++ b/src/webenginewidgets/api/qwebenginepage.cpp
@@ -594,6 +594,9 @@ void QWebEnginePagePrivate::javascriptDialog(QSharedPointer<JavaScriptDialogCont
         if (accepted)
             controller->textProvided(promptResult);
         break;
+    case InternalAuthorizationDialog:
+        accepted = (QMessageBox::question(view, controller->title(), controller->message(), QMessageBox::Yes, QMessageBox::No) == QMessageBox::Yes);
+        break;
     default:
         Q_UNREACHABLE();
     }
-- 
cgit v1.2.3