ZMYaro / paintz

A simple drawing app that runs in a web browser, designed to be an MS Paint substitute for Chromebooks and other Chrome OS devices. PaintZ is free, but please consider supporting development at https://ko-fi.com/ZMYaro or https://patreon.com/ZMYaro.
https://paintz.app
53 stars 11 forks source link

Selecting all sometimes fills with the fill color #255

Closed ZMYaro closed 1 year ago

ZMYaro commented 2 years ago

Describe the bug Sometimes, using the “Select all” function fills the canvas with the current fill color until the selection is moved.

Steps to reproduce the behavior

  1. Open a fresh PaintZ window or open an image.
  2. Select the rectangular selection tool.
  3. Select an arbitrary region.
  4. Select the ”Select all“ button (or Ctrl+A).

Expected behavior The entire canvas should be selected.

Actual behavior The entire canvas gets selected, but the selection is filled with the current fill color until the selection is transformed.

Environment

ZMYaro commented 2 years ago

https://user-images.githubusercontent.com/763405/186576751-b5f16db8-b7aa-4b42-ba40-96fbe278e120.mp4

ZMYaro commented 2 years ago

With a friend's help, I we ruled out

I am going to assume this is a bug in Chrome for Windows and not prioritize looking into it for now unless it starts happening elsewhere, but I will leave it open for now just in case.

lizzyd710 commented 2 years ago

I know you already tested on a bunch of platforms but just to help be thorough, tested on Red Hat Linux (RHEL 9), with Firefox 91.12.0esr and it didn't happen for me. Let me know if you want me to test any other browsers on this platform!

ZMYaro commented 2 years ago

@lizzyd710 Thank you for checking that!

ZMYaro commented 2 years ago

Note for future!me: I had PaintZ 3.2 cached in one of my test browsers on one of my Windows machines, and it still happens there (Chrome 107), so it was not caused by the selection tool changes in PaintZ 3.3.

ZMYaro commented 1 year ago

This appears to be resolved in the stable release of Chrome 107, so it seems this was a Chrome bug that has been fixed.