Looks like the BrowserWindow events at the js api level are unchanged for the past two years.

Here's hoping something deeper was broken about them that now drastically changes top-level api behaviour!