ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

In single process mode, webviews always use the default WebContext (and
WebView.context is basically read-only). When running an application
with OXIDE_SINGLE_PROCESS in the environment, we allow an application
provided WebContext to become the default WebContext, so that you can
run most existing applications (assuming they only ever create a single
context) with OXIDE_SINGLE_PROCESS and they won't break.

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.

** Affects: oxide
     Importance: Medium
     Assignee: Chris Coulson (chrisccoulson)
         Status: In Progress

** Changed in: oxide
    Milestone: None => branch-1.15

** Changed in: oxide
     Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
       Status: New => In Progress

** Changed in: oxide
   Importance: Undecided => Medium

-- 
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/1565050

Title:
  Allow the first created WebContext to become the default context in
  single process mode

Status in Oxide:
  In Progress

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_PROCESS in the environment, we allow an
  application provided WebContext to become the default WebContext, so
  that you can run most existing applications (assuming they only ever
  create a single context) with OXIDE_SINGLE_PROCESS and they won't
  break.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1565050/+subscriptions