As discussed in https://chromium-review.googlesource.com/c/chromium/src/+/741344#message-3b7b2b709eb52a77780db5667aec1d9d175a81b4

the hung renderer dialog is based on WebContents and not at the level of renderers.

Does it make sense to support this dialog if a OOPIF is unresponsive.

There are two sides to this discussion:
1) Some OOPIFs are bad and we don't really care if they receive events as it won't cause a real issue
2) Some OOPIFs that hung and the user isn't able to interact with them can be problematic for the user to discover.

We should decide what to do with OOPIFs and hung render dialogs. This came up in discussions around what to do with the event hit testing timeout sadrul@ is going to implement.