WebContentsObserver is a widely used way of interacting with content/ right now. Many of those implementations will need to be converted to using the Content service instead. I'm currently investigating what the API replacing WebContentsObserver would look like in the content/ service world.