[Bug]: Layers not working as expected about openoutpaint HOT 10 CLOSED

It suddenly fixed itself today 😳 I swear that yesterday I still fought with it but today it's fine 😅

from openoutpaint.

Im primarily used Brave, now with Chromium Version 120.0.6099.71. the issue seems to be gone. It´s working for me now, but i can give everyone the advice to check the settings. Many Browsers tend to change the settings after an update an reactivate Adblockers and so on. This can cause issues with send pictures to... option.
@zero01101 thank you for your work, im working with python and stable diffusion for 6 Months now and still fail at simple tasks. So thumbs up for this tool you share with us.

from openoutpaint.

disclaimer: apologies for the extended delay, my brain is terrible and you shouldn't expect much from me)

you've got new layer per dream enabled i presume? i can't reproduce the layer merge issue, can you export a workspace after this occurs and upload it?

from openoutpaint.

I also have layers problem since the chrome latest update:
when I have 2 layers and I try to merge them together - instead of merging the two layers content, It leaves only the top layer's content and removes the bottom layer's content.
Also - when I work on one layer and have content in it, when I make img2img or dream action upon it and approve the result, the only content that remains is the content just made by the said img2img/dream.
I can play with the History stages to get the content back, but it's annoying.

from openoutpaint.

more disclaimer: i warned you my brain is terrible and you shouldn't expect much from me lol

confirming miserable garbage with merging as well as new dreams deleting previous layer contents without new layer per dream in chromium-based browsers - likely both the same issue with whatever new canvas "feature" has been recently implemented in chromium...

from openoutpaint.

so hey, uh this potentially APPEARS to be an upstream issue with chromium, because with chrome v119.0.6045.200 (Official Build) (64-bit) on win11x64 i'm no longer experiencing this at all? edge seems to still be affected and i haven't tried brave/opera/other chromium-dependent browsers but given that chrome itself works, i bet the rest will see the issue alleviate with time...

can anyone else confirm if the issue is gone on most recent chrome?

from openoutpaint.

Still happening to me on Chrome, Version 119.0.6045.200 (Official Build) (64-bit). Even went into Incognito mode to rule out an extension doing it.

from openoutpaint.

Me too, still happening 119.0.6045.200 (Official Build) (64-bit) (win-11)

from openoutpaint.

ok ok i swear i'm gonna lose it or all of you are conspiring to troll me really effectively lol; i have tested the following successfully:
win11x64
chrome Version 120.0.6099.71 (Official Build) (64-bit)
edge Version 120.0.2210.61 (Official build) (64-bit)

mac m1 pro sonoma
chrome Version 120.0.6099.62 (Official Build) (arm64) AND .71

i was 100% admittedly experiencing it on edge when chrome 119.blah was working so i figured it had to be a "my machine" quirk but this is now multiple browsers, multiple machines working as expected after recent updates to chromium upstream...

licecap was being uncooperative on mac but i swear to god it worked as expected lmao

please god anybody confirm because i can not figure out why this is happening otherwise 🤞 🙏

also bless you papa firefox <3

from openoutpaint.

tentatively closing because i THINK this is "fixed" now but by the grace of google and chromium upstream 🤞

from openoutpaint.