[Bug]: Latest branch bugs out the stop button

[Dajova]

Checklist

• The issue exists after disabling all extensions
• The issue exists on a clean installation of webui
• The issue is caused by an extension, but I believe it is caused by a bug in the webui
• The issue exists in the current version of the webui
• The issue has not been reported before recently
• The issue has been reported before but has not been fixed yet

What happened?

fafb0b5
This branch makes the stop button for generations unusable. No matter what model i use, it doesnt stop the generation, even tho the UI indicates that it's stopped. And the only way to stop it is to close the console window itself.

Steps to reproduce the problem

• update to latest branch.
• start generating anything.
• stop the generation.
• keeps on generating.

What should have happened?

Should just stop generating the current batch.

What browsers do you use to access the UI ?

Firefox.

Sysinfo

Console logs

-

Additional information

No response

[anapnoe]

please test also with chrome browser
it should work on firefox if you Go to the Firefox about:config page, then search and toggle layout. css.has-selector. enabled

[Dajova]

Did. tested firefox, chrome and edge, neither was able to stop the generation once it started. All browsers indicated that the generation was stopped in the UI, but kept on generating regardless.

edit: i think i may have found the culprit, but it started happening with that commit regardless, so it seems like a incompatibility issue.
https://github.com/ilian6806/stable-diffusion-webui-state is the extension.

edit2: Nwm, I hard-resetted/reinstalled the latest commit and it was still doing it, even after disabling that extension. Something is clearly wrong in the build.

edit3: Ok.., now it only triggers with the WebUI State extension again after i've applied latest 5 major commits again. I have no idea what's going on at this point.

edit4: Nwm again, now it just seems to stop working randomly. One batch was working fine and then the next one, it stops working again. It's infuriating.

[Dajova]

Ok, it seems this wasn't a bug after all, it was just a new option that was undocumented and enabled by default. Disabling this and it's fine again.