In SingleProcessMash and Mash, during login, we set the event targeting policy of the status bubble to NONE to temporarily disable receiving events https://cs.chromium.org/chromium/src/chrome/browser/ui/views/status_bubble_views.cc?type=cs&q=status_bubb&g=0&l=659. This is causing a DCHECK to fail in window::SetEventTargetingPolicy (https://chromium-review.googlesource.com/c/chromium/src/+/1260511/12/ui/aura/window.cc) that we don't reset it after creating the layer-tree-frame-sink. This is related to bug https://bugs.chromium.org/p/chromium/issues/detail?id=877762 trying to fix Viz hit-testing on ChromeOS with the exo-shell-surface. I'm going to temporarily change the event-targeting policy to not be NONE in Mash when login and fix it separately after that CL to either
1) change Viz hit-testing to be able to update hit-test data when updating event-targeting policy
2) look into if it's necessary to change the event-targeting policy to NONE during login or if there's a better way to prevent processing events during login