| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
The simplest adaptations to API and build changes in Chromium 55
Change-Id: I923fa188690a04902492317807f72f006bcab9c6
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
|
|
|
|
|
|
|
| |
With CookieMonster now being the CookieStore, it must only be accessed
from the IO thread like the CookieStore, so we need to pass calls to the
IO thread and back.
Change-Id: Icb6d6008c08cfe006c4c1bc2324824223cb82fba
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
| |
Update files using old header.LGPL3 to use header.LGPL
Update files using old header.FLD to use new header.FDL
Update files using old header.BSD to use new header.BSD
Change-Id: I36a67aaa8c3ca6c7946308defc9c03c3571a7d23
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: I8f9a4c5c155a65ede24908799218fd867db0767c
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
Replace QList with QVector in all places where the type isn't a pointer,
and is not already (indirectly) exposed through public API.
Change-Id: I90e3db56bf9ebda6b3cb8fb4396d2ae283159727
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
| |
This patch adds acceptCookie virtual function that is
called when a request wants to set a new cookie and
can be overridden to intercept or block these cookies.
Change-Id: I8b932d4176ffc3c0ac48b1656486d5492cabaefd
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This tests the part of the cookie API that can be tested locally.
The notification about third-party cookies (acceptCookieFromUrl)
can not be tested locally since it requires cookies to be set from
a different domain than the main frame, which requires a remote
host or a local web server with support for virtual DNS.
Testing requires the ability to set cookies for local pages loaded
through the qrc scheme.
We could eventually extend this in the future to enable setting cookies
on registered custom schemes, but for that we might have to implement
our own cookie store.
Since Chromium's cookie store relies on source url's to manage cookies
and qrc:// cookies do not specify a domain, a specific source url is
needed to be able to delete an individual cookie that has been set by
a page loaded through qrc://.
This patch requires a new function on QNetworkCookie to be able to
forward the source url of the cookie to Chromium.
Change-Id: I97dd04b27fbb8ec63060f9b741ad65c29a773a6c
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
| |
This patch adds support for deleteSessionCookies, deleteAllCookies
and getAllCookies to make these features directly accessible without
the need of subclassing QWebEngineCookieStoreClient and having to
implement a less efficient equivalent.
Change-Id: I6645bee7fcef38d00dccfaa81f4e9ada86c491df
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
This callback is no longer available from Chromium, and was not very
important to the API in the first place.
Change-Id: If65509380f2c27053cb4c04801b4e50694440d6a
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
|
|
|
This class or its subclass can be set on the
QWebEngineProfile and its API enables intercepting
Chromium's cookies, setting and deleting cookies
in the cookie store.
These functions are asynchronous so if the result
of the task is needed the user can provide a
callback which will be run on the calling thread
when the requested operation finishes.
This does not include a hook for QQuick layer yet,
there we have to figure out what the most convenient
way is from a developer's perspective.
Change-Id: I6a3af071883ce632df7a2fb952da93f306ac3fe2
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.com>
|
