diff options
| author | Alexandru Croitor <alexandru.croitor@qt.io> | 2017-05-09 18:49:59 +0200 |
|---|---|---|
| committer | Jani Heikkinen <jani.heikkinen@qt.io> | 2017-05-15 06:24:28 +0000 |
| commit | 95b88ad5fe21200c28744301309a8408d82758b8 (patch) | |
| tree | cf110a927828af70063bdbc455e3382311fe4338 /src/webengine/doc/src/qtwebengine-platform-notes.qdoc | |
| parent | 28290da35893756767baccca644d2b9a261945a3 (diff) | |
Document Mac App Store incompatibility
The patch also removes the appstore compatibility feature
from the feature summary displayed when qmake is invoked, and
also makes sure not to pass the relevant compatibility argument
to GN.
[ChangeLog][macOS] Removed -appstore-compliant configure switch.
Task-number: QTBUG-60443
Change-Id: I9c5ced0375195dd62e2416c57484d8e6021ebdd8
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Diffstat (limited to 'src/webengine/doc/src/qtwebengine-platform-notes.qdoc')
| -rw-r--r-- | src/webengine/doc/src/qtwebengine-platform-notes.qdoc | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/src/webengine/doc/src/qtwebengine-platform-notes.qdoc b/src/webengine/doc/src/qtwebengine-platform-notes.qdoc index 57e3ce6a8..2eeda6e8a 100644 --- a/src/webengine/doc/src/qtwebengine-platform-notes.qdoc +++ b/src/webengine/doc/src/qtwebengine-platform-notes.qdoc @@ -114,17 +114,18 @@ \section1 Mac App Store Compatibility - By default, Qt WebEngine uses private \macos API, which might cause an application to be - rejected when submitted to the Mac App Store. To configure Qt WebEngine not to use these API - calls, Qt has to be reconfigured with the \c -appstore-compliant switch. - - However, this will cause some behavioral changes, such as: + Applications using Qt WebEngine are not compatible with the Mac App Store, because: \list - \li The \macos Kill Ring functionality will no longer work (emacs-like copy pasting). - \li Certain Chromium sandboxing cleanup is not done. - \li Text areas will be painted with a different style. - \li Text fields might be painted with a different style on Mountain Lion (\macos 10.8). + \li The Chromium part of the code uses several private API methods, which are prohibited by + the App Store. + \li Applications submitted to the App Store must be code-signed with the App Sandbox feature + enabled. The App Sandbox feature interferes with Chromium's own sandbox + initialization, which results in Chromium not being properly initialized. This also + ties in with the private API usage. Furthermore, standalone Chromium itself is not + officially tested with the App Sandbox enabled, and even if work is done to bypass + the App Store's restrictions, that would not guarantee correct behavior of the library. + \endlist \section1 macOS Airplay Support on MacBooks with Dual GPUs |