Public bug reported:
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.
** Affects: oxide
Importance: Low
Status: Triaged
** Changed in: oxide
Importance: Undecided => Low
** 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/1469139
Title:
OxideMsg_SetUserAgent should be sent from inside
content::NOTIFICATION_RENDERER_PROCESS_CREATED
Status in Oxide Webview:
Triaged
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
--
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
