| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a wrapper designed to handle profile construction.
The QWebEngineProfile class allows the modification of profile storage
properties, which is against chromium profile design. Changing storage
properties requires the recreation of storage and network context
leading to hacks, which in turn leads to bugs.
The QWebEngineProfileBuilder aims to prevent modification of storage
properties and set them at the profile creation time. The current change
introduces new APIs without deprecating the storage setters in the
QWebEngineProfile class. The final goal is to deprecate the storage
setters and constructor from QWebEngineProfile and use the
QWebEngineProfileBuilder to create profiles.
Task-number: QTBUG-66068
Change-Id: I3c2562c9e1445708f0dbdeae5783a8c7d38313af
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit contains fixes for the issues found during the API review
of the new permissions API. In particular:
- All new enums are now scoped
- Replaced isTransient with its opposite, isPersistent
- Renamed Feature to PermissionType
- Made origin() return a non-const QUrl
- Renamed PersistentPermissionsPolicy members to be more concise
- Fixed a couple of bugs in the implementation
- Updated documentation
Change-Id: Idf84e1c9ba3ae803ef4686e1caa7f3e6c198c87d
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Fix compiler warnings that are related to QWebEnginePermission.
Pick-to: 6.8
Change-Id: Icac1352e4934f73a205b85896b6f83171b759dd3
Reviewed-by: Kaloyan Chehlarski <kaloyan.chehlarski@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the addition of permission persistence, it's now important for us
to have an API for querying previously granted/denied permissions, so
that they can be revoked at a later point. This change does the bulk
of the work to get us there, by introducing a new type representing
a single permission for a given URL/Feature pair.
This type holds no information about the permission's state; it is
simply an accessor object which allows its user to query the current
status of the permission, grant/deny it, or reset it back to its
initial state (so, delete it from storage). This provides application
developers an easy way to store/modify lists of permissions without
having to define their own custom types. A subsequent change will expand
the API to provide a list of all permissions for a given profile.
The current API (in QWebEnginePage and QQuickWebEngineView) has been
marked as deprecated, but has not been disabled to ensure a smooth
transition for developers.
[ChangeLog][QtWebEngineCore][QWebEnginePage] Deprecated old
permissions API
[ChangeLog][QtWebEngineQuick][WebEngineView] Deprecated old
permissions API
[ChangeLog][QtWebEngineCore] Added new API for querying and modifying
website permissions.
[ChangeLog][QtWebEngineQuick] Added new API for querying and modifying
website permissions.
Pick-to: 6.8
Change-Id: I8661cdc26bbd6dcde6403d29cc083bcea1a49ccc
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
We have now extra call to enable push messaging, therefore
drop usage of simple browser in example and use
the same code as in Notification Example but add new settings
and fix profile to be not off-the-record.
Task-number: QTBUG-107442
Pick-to: 6.5
Change-Id: I3069c4cf2b6a6ce864c1e4c578ab03adb67984e4
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|
