Currently, the VR URL bar pulls state directly from WebContentsObserver callbacks. For consistency, a ToolbarModel instance should be created and used instead.
This should cut down on inconsistent visuals on page transitions, and reduce the likelihood of security bugs in corner cases.
Use of ToolbarModel has bee prototyped and looks quite possible. Note that the trigger to poll the ToolbarModel may still be WebContentsObserver based (TBD), as the model does not provide a callback indicating when it's reported state changes.
Comment 1 by ddorwin@chromium.org
, Jun 26 2017