Currently, a page load metrics observer owns the pause resource loading handles and triggers capped pages. We should consider moving this functionality/ownership to a different WebContentsObserver and just source information from page load metrics to that WebContentsObserver. 
 

Currently, a page load metrics observer owns the pause resource loading handles and triggers capped pages. We should consider moving this functionality/ownership to a different WebContentsObserver and just source information from page load metrics to that WebContentsObserver. 

Typically, PLM observers do not modify the state of the page, which page capping does. Typical "TabHelpers" which are WCO's are more closely aligned in design with page capping than PLM observers. There are some technical concerns about supporting a WCO that gets messages from a PLM observer, so those need to be investigated before moving.