Allow the first created WebContext to become the default context in single process mode
Bug #1565050 reported by
Chris Coulson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Fix Released
|
Medium
|
Chris Coulson |
Bug Description
In single process mode, webviews always use the default WebContext (and WebView.context is basically read-only). When running an application with OXIDE_SINGLE_
When setting single process via the API, we don't allow any application provided WebContext to become the default. This is making it difficult to run tests though, where we do want to create a TestWebContext and have it used by webviews during the tests.
Related branches
Changed in oxide: | |
milestone: | none → branch-1.15 |
assignee: | nobody → Chris Coulson (chrisccoulson) |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in oxide: | |
status: | In Progress → Fix Released |
To post a comment you must log in.