Public bug reported:
CookieManager methods all return an error (-1) if they are called before
the WebContext is initialized (ie, its BrowserContext has been created).
A WebContext is currently only initialized when it's attached to a
WebView
** Affects: oxide
Importance: Low
Status: Triaged
** Summary changed:
- Using CookieManager should initialized the WebContext
+ Using CookieManager should initialize the WebContext
** Changed in: oxide
Status: New => Triaged
** Changed in: oxide
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1439463
Title:
Using CookieManager should initialize the WebContext
Status in Oxide Webview:
Triaged
Bug description:
CookieManager methods all return an error (-1) if they are called
before the WebContext is initialized (ie, its BrowserContext has been
created). A WebContext is currently only initialized when it's
attached to a WebView
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1439463/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
