OxideMsg_SetUserAgent should be sent from inside content::NOTIFICATION_RENDERER_PROCESS_CREATED

Bug #1469139 reported by Chris Coulson on 2015-06-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Low
Chris Coulson

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.

Changed in oxide:
importance: Undecided → Low
status: New → Triaged
Chris Coulson (chrisccoulson) wrote :
Changed in oxide:
milestone: none → branch-1.9
status: Triaged → Fix Released
assignee: nobody → Chris Coulson (chrisccoulson)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers