ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

This was fixed with http://bazaar.launchpad.net/~oxide-
developers/oxide/oxide.trunk/revision/1150

** Changed in: oxide
       Status: Triaged => Fix Released

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

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

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

Title:
  OxideMsg_SetUserAgent should be sent from inside
  content::NOTIFICATION_RENDERER_PROCESS_CREATED

Status in Oxide Webview:
  Fix Released

Bug description:
  We send OxideMsg_SetUserAgent inside
  ContentBrowserClient::RenderProcessWillLaunch, but this should be
  moved to an observer of the
  content::NOTIFICATION_RENDERER_PROCESS_CREATED notification, which is
  fired before other queued messages are sent to the render process.
  This will ensure that the process is properly initialized before
  starting any navigations.

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