This has already been filed as an issue --> https://github.com/Scirra/Construct-3-bugs/issues/1396
Where Ashley said that itÂ´s an issue with chrome --> https://bugs.chromium.org/p/chromium/is ... ?id=823247
Where it was fixed a couple of days ago actually. Based on https://www.chromium.org/blink/when-wil ... -or-canary this will take ~10 weeks before itÂ´s shipped into the stable chrome version, so we need patience, or use https://www.google.com/chrome/browser/canary.html (I wouldnÂ´t though)
The problem is if you search for the issue on github (with "zoom") you will not find it unless you delete the "is:open" because Ashley closed this error. I think what would be great is some sort of bugtracker, possibly even inside of construct, that shows the current open bugs and if they are beeing worked on. So if you encounter an error, you could quickly check if itÂ´s already been filed aswell as itÂ´s status without even leaving construct. This will likely lead to some amount of overhead, but also might lead to reduce duplicate bugreports and frustration. I mean the bug has already been filed, fixed and will roll out soonish, so a user shouldnÂ´t be left uninformed needing to make a "help pls" thread, and Ashley doesnÂ´t need to be told for the 15th time that there is a bug.
At minimum, Ashley shouldnÂ´t close an issue unless itÂ´s actually been 100% fixed and released, because else users wonÂ´t find it (that easy) when they search for it and just end up filing them again, posting suggestions, make threads about it, etc. I personally almost filed that zoom issue again recently, I donÂ´t even know anymore how I found out it has actually been filed and is beeing worked on already.