You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 1.5.5 from the store, it looks like the canvas is still injected even if all the drawing options are turned off (trail+action+text).
It shouldn't be important, except for 2 reasons :
I use the "Dark Reader" extension (with "static" setting), which invert a lot of colors, including the canvas when I start a mouse gesture, blacking out the whole screen. It's not a big bug, but it's annoying, especially since I have a tendency to start a gesture before finishing reading the page.
By trying to debug it, I saw that there was code to handle that case, but it didn't seem to work, and that bothered me. In particular, that snippet
When debugging, I saw that Chrome didn't go inside the if, even if ! this.option.isTrailOn() was true when typed in the console.
I don't know typescript, and I'm almost a noob about extensions, so I'm not sure what is the issue. Maybe this particular snippet gets removed when "compiling" it ? I have no idea.
In any case, I have created a workaround for myself, by setting the canvas z-index to -10000. That's good enough for me right now, but I thought you should know.
The text was updated successfully, but these errors were encountered:
In 1.5.5 from the store, it looks like the canvas is still injected even if all the drawing options are turned off (trail+action+text).
It shouldn't be important, except for 2 reasons :
When debugging, I saw that Chrome didn't go inside the
if
, even if! this.option.isTrailOn()
was true when typed in the console.I don't know typescript, and I'm almost a noob about extensions, so I'm not sure what is the issue. Maybe this particular snippet gets removed when "compiling" it ? I have no idea.
In any case, I have created a workaround for myself, by setting the canvas z-index to
-10000
. That's good enough for me right now, but I thought you should know.The text was updated successfully, but these errors were encountered: