On Thu, Sep 30, 2021 at 09:08:03AM +0100, Carsten Haitzler wrote: > On Wed, 29 Sep 2021 11:43:33 -0700 Marc MERLIN <marc_...@merlins.org> said: > > > On Wed, Sep 29, 2021 at 08:17:25AM +0100, Carsten Haitzler wrote: > > > did you see my other mail in response to this to you, this list and also > > > cc'd adun...@igalia.com with a link to the commit? > > > > I missed it, there may be something wrong with my Email (I'm at a conf, > > need to check later). > > > > > yes - a workaround commit is in e git. chrome should decidedly not be > > > setting CSD properties on a window that is not CSD though (it seems to add > > > them later after the initial map i think). this leads e to go into a logic > > > "hole" where it has decided the window is non-CSD when a new client window > > > is managed (correct) but then later gets property updates for CSD > > > properties .. though these say the CSD frame area is 0 0 0 0 - this hybrid > > > nature of property info led e to treat the window partly as CSD and partly > > > as traditional SSD. if chrome did not put the _GTK_FRAME_EXTENTS property > > > that mark it as CSD on the window it'd not be confused. > > > > Thanks for that update. That said, from what you're saying it is still a > > bug/problem in chrome M95, correct? > > If so, adun...@igalia.com, are you able to adjust the code accordingly? > > yes. i added a comment in that bug now at the end - it's a bug in chrome - > adding that property is confusing. on one hand the window should be SSD not > CSD > but it's setting CSD properties. this leads to e having a logic "black hole" > that shouldn't happen - the situation makes no sense, but e didn't have checks > for the "nonsensical" situation - thus e behaved weirdly leading to your > results. i patched that over to handle that weirdness, but this may affect > other WM's too as they may not guard against "silly property combinations from > the client" in all cases.
Thank you very much for trying this out, the workaround in E, and the details that will hopefully help getting M95 fixed. I pasted what you wrote in the bug. Thanks again Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08 _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users