It's happening since a few weeks. Here are the video's.

Deleted: mab-fout.mov 866 KB

mab-fout.mov 866 KB Download

Deleted: lijnen.mov 988 KB

lijnen.mov 988 KB Download

Tested this on Windows-10, chrome versions: 53.0.2785.116, 55.0.2876.0 & 50.0.2624.0 and observed black patches when dragging the box around. However the same works fine on Mac OS 10.11.6 , chrome version: 55.0.2876.0 and 53.0.2785.116. Box rendered fine when dragging the same on Mac OS 10.11.6.

Attached is the screen-cast from Windows on the latest and older stable versions.

tim.vde@: Could you please review the screen-casts and confirm if the issue seen on Windows is same as in the attached screen-cast.

Deleted: 651341_M50.mp4 1.7 MB

	651341_M50.mp4 1.7 MB View Download

Deleted: 651341_M53.mp4 2.2 MB

	651341_M53.mp4 2.2 MB View Download

Yes I can confirm that this is the same issue! Really glad that you can reproduce it.

The version on OSX where we can reproduce is: 10.10.5 (see the report) 

Don't have OS 10.10.5 to confirm the issue on Mac, but issue is reproducible on Windows-10 and is non-regression issue as same behavior is seen on chrome version: 45.0.2454.101. Chrome versions before that on Windows doesn't play the content and Flash player isn't supported on older chrome version. 

Note: Worked fine on Mac OS 10.11.6.

Most of our users are Windows users, if it's fixed for Windows we would be very grateful. 

On 10/1 when I first tried this issue on my Win7 x64 PC (FP 23.0.0.162 + Chrome 53.0.2785.116 64-bit), it was super easy to reproduce this issue, but today I am not able to see the problem anymore.

I noticed that Chrome has updated to a new revision - 53.0.2785.143, so I tried to fall back to the previous one - 53.0.2785.116, but I still could not reproduce the problem. I guess it may be because of nVidia graphics card driver update? I am not sure.

I am wondering whether this problem is reproducible with current Chrome release?

We'll check that out. I have a colleague who was able to reproduce this. I check if it's still possible with the latest release.

We've changed the wmode to direct temporarily. This solves this issue but we need to use wmode=transparent because we need the transparency. I thinks that's why you cannot reproduce.

I'm still able to reproduce the issue with the most recent version of Chrome.

See attached video.

Deleted: flash-bug.mp4 5.5 MB

	flash-bug.mp4 5.5 MB View Download

@tonynadhoc@gmail.com when we make the change to "wmode" and delete the object element by following the video, it does not re-appear, we wonder how can we make that happen? 

I tried to treat "wmode=direct" the same as "wmode=transparent" in flash player so that I can reproduce the problem, and I think we have fixed it.

In order for QE to verify the fix, we'd better follow your instruction, that's why we may need your help on how to change "wmode" in the drawing tool webpage correctly.

He did command + Z to Undo the delete action. Then the element is inserted again with the wmode transparent.

A quicker solution is by using these links:
https://www.gynzy.com/en/#!/items/mathematics/number-pieces/17/2747&electron_app=true
https://www.gynzy.com/en?electron_app=true

This forces wmode to transparent in our website. We use transparency in our Electron app that wraps our website to make it partially transparent.

@1575804052 @xzh...@adobe.com Did QA verify your fix? Are the steps clear? Can we do anything to speed things up? 

@tim.vde@gmail.com QA has verified the fix using the trick mentioned in comment 13. I believe the fixed version of flash player should be available in next beta build.

@xzh...@adobe.com That's great to hear! Could you give us the version number that contains the fix when it's available? Is there a changelog where we can keep an eye on? 

@tim.vde@gmail.com the version number should be >= 23.0.0.196. Which changelog are you referring here? The bug fix description?

I guess the chromium changelog. We really want to know when the fix gets in beta and stable so we can check and inform our users. What description will be in the changelog? 

The version you are referring to is the Flaherty Player version? 

The status of this issue hasn't changed while it's fixed for next beta build. 

We just released a beta binary to Google this morning, the flash player version is 23.0.0.198, I guess the channel will be updated soon.

@xzh...@adobe.com We've tested flash player version 23.0.0.205. But it's still possible to reproduce so it's not solved :-(.

I made an error with the correct URL to check the fix, it should be https://www.gynzy.com/en?electron_app=1 (then wmode=transparent) 

Please have another look at this issue please.

@tim.vde@gmail.com Could you reproduce this issue with the current Chrome Canary build?

@xzh...@adobe.com 
In the current Chrome Canary build, we cannot write at all on our board. We can interact with a mouse, but when we use our Interactive Whiteboard, click & drag is not working. 
We have a SmartBoard installed, from SmartTech: 
https://support.smarttech.com/en/hardware/interactive-whiteboards/smart-board-800

We have Chrome Canary version 56.0.2906.0 (Windows 64-bit) installed
in combination with Flash Player version 23.0.0.207

I've attached a movie to demonstrate the problem. We switch between the normal Chrome browser with Flash Player .205 and Chrome Canary with Flash Player .207
As you can see in the movie, we cannot interact at all using our Interactive Whiteboard in Canary. The "normal" Chrome browser is working as expected.

Just to be sure, we tried all chrome://flags touch settings, but we couldn't find a setting to fix the digiboard writing issue.

We also have good news: we cannot reproduce the artifacts anymore in Chrome Canary.

Deleted: chrome_canary_writing.mp4 4.4 MB

	chrome_canary_writing.mp4 4.4 MB View Download

@a.debonth@gynzy.com

The reason that build 23.0.0.205 still has the problem is that this build is actually a security patch fix, it is still based on previous release which 23.0.0.185, that's why you can still see the problem. Build 23.0.0.207 is the really beta release, you can test it with Chrome stable and Chrome beta to see if it fixes the artifact issue.

Regarding the interactive issue, my recommendation is to copy FP build 23.0.0.207 from Canary into Chrome stable/beta, and copy FP build from Chrome stable/beta to Canary, to see whether it is an injection of Flash Player or Chrome.

@xzh...@adobe.com 

I've tried copying from Canary to Stable but the PepperFlash/23.0.0.207 folder is removed when I run Chrome Stable. I then see the 23.0.0.205 folder reappear.

Do you have instructions how to do this? 

@tim.vde@gmail.com

You can try copying just the pepflashplayer.dll, not the whole folder.

xzh...@adobe.com

Is that the only option? We've tried a couple of things.  We will double check. 

⁣​

@tim.vde@gmail.com

You can also use command line to launch Chrome to specify PepperFlash path:

<path-to-chrome>/chrome.exe --ppapi-flash-path=<path-to-PepperFlash-dll> --ppapi-flash-version=25.1.0.0

the version number just needs to be bigger than the current one.

@xzh...@adobe.com

It looks like 23.0.0.207 is the last 23.x version. version 24 is in beta, when is this version expected to be released? We're preparing a new version of our Electron app with the Flash Player bundled and would like to add the latest version. But we don't feel happy bundling a beta version. Else we have to keep waiting for a stable release and release a new version of our Electron app with an updated flash player only.  

@tim.vde@gmail.com As far as I know, the official release date should be next Tuesday.