+a bunch of folks.

A couple of things:

1. Layer lists was a longer term suggestion in the doc. We don't deal with them yet. I do think submission of CompositorFrames and input event ACKs are good signals for "responsive" though.

2. I think the window manager will likely want a signal for when an app goes unresponsive, and another signal for when the app is responsive again.

WDYT?

(2) you're likely right. I wouldn't add the api until we have a concrete use case. But I think you're right.

This is very similar to 576305. If we had 576305 mus could use it and forward to the windowmanager.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

jonross@ please triage as appropriate.

per discussion in slack, largely subsumed in WindowManager::WmClientJankinessChanged

Also the window_property ash::mus::kWindowIsJanky is already in use for UI updates