On Tue, 28 Sep 2021 21:42:11 -0700 Marc MERLIN <marc_...@merlins.org> said:
> On Thu, Sep 23, 2021 at 09:00:44AM -0700, Marc MERLIN wrote: > > There are 2 different issues. What you describe is known broken in M94 > > and fixed in M95. > > The 23/24 pixel offset is related but different, and still broken, but > > apparently only with E. That's what we need help with. > > Carsten, were you able to get an M95 build to test/reproduce? > We only have to much time to get it fixed before it becomes harder and > potentially breaks all E users. 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? 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. > Or adun...@igalia.com, if you have a way to install E on your machine > and see if you get this too? > > Thanks, > 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 > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
