Hi fellow Awesome users, I've encountered some annoying behavior with web notifications on Chrome and Firefox, and I was wondering if others had seen this behavior before me and if they were able to remedy it.
My problem is this: when I see a web notification (https://developer.mozilla.org/en-US/docs/Web/API/notification) displayed, it always appears on screen 0 of my two monitor set up, even if the browser displaying the notification is on screen 1. As I tend to put "back burner" stuff on screen 0 and primarily work off of screen 1, this causes me to sometimes miss web notifications, which is pretty annoying. Ideally, I would like them to show up in the upper right corner of screen 1, where I have naughty displaying its notifications. However, after digging around, I've found that the X11 windows used to implement these notifications do not generate client manage events; in fact, they don't generate any events that are exposed to the Lua API, as far as I can tell. It seems that they generate a map notify (rather than a map request, and not to be confused with a mapping notify) event, which awesome doesn't seem to handle. Has anyone seen this behavior and come with a good solution for their rc.lua? If not, developers of awesome: would you be open to a patch exposing map notify events via the Lua API so that users may handle this scenario? Thanks, Rob -- To unsubscribe, send mail to [email protected].
