ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

This was implemented the way it is today because it was originally used
for user agent string overrides and we wanted to keep everything on the
IO thread. That no longer applies though, and the API really sucks to be
honest.

We should replace this with a traditional signal / slot mechanism and
make the notifications asynchronous where Chromium allows.

** Affects: oxide
     Importance: Medium
         Status: Triaged

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

** Changed in: oxide
       Status: New => Triaged

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

Title:
  Replace WebContext::networkRequestDelegate with a signal / slot
  mechanism

Status in Oxide:
  Triaged

Bug description:
  This was implemented the way it is today because it was originally
  used for user agent string overrides and we wanted to keep everything
  on the IO thread. That no longer applies though, and the API really
  sucks to be honest.

  We should replace this with a traditional signal / slot mechanism and
  make the notifications asynchronous where Chromium allows.

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