Clip region in HTML5 canvas not working as expected
Reported by
cmw...@labci.com,
Apr 15 2016
|
|||||||
Issue description
Chrome Version : 50.0.2661.75
Other browsers tested:
Firefox: OK
IE: OK
Please refer to the attached picture.
The top canvas shows a red region and a blue region and their intersection is thus shown as purple.
In the bottom canvas, the red region is changed to a clip region. The result should show only the purple intersection.
The testing HTML is attached for reference
,
Apr 18 2016
What is your OS and GPU model? There is a known issue with clipping on Windows systems with AMD GPUs. See issue 597107
,
Apr 19 2016
I am using a ThinkPad Edge core i5 notebook, Intel display, and Win7 I've also tried another desktop running Win8, Intel display, and has the same problem. I didn't have this problem before and see it after a recent chrome upgrade. Thanks
,
Apr 19 2016
We just landed a fix that resolves clipping on all devices where Chrome is using DirectX9, which may include your system. Please download an install the Chrome Canary: https://www.google.com/chrome/browser/canary.html You can install Canary alongside a regular installation of Chrome (no need to uninstall anything). This is our nightly build, which includes the recent fix. Let us know if it solves your issue.
,
Apr 20 2016
Sorry, doesn't seem to fix the problem
,
Apr 20 2016
Just tested it in my Android Chrome (v47), it's OK
,
Apr 20 2016
Verified this issue on Windows 7 for Google Chrome Canary Version - 52.0.2713.0 and attached is the output. @cmwong: Could you please have a look at the attached attachment and let us know if this is the correct behavior. Else, please provide us the screen-recording for better understanding. Thank you.
,
Apr 20 2016
I would expect things to be OK in Chrome 47. The clipping bug we are aware of appeared in Chrome 49, and became more widespread in Chrome 50 (current stable release). It is fixed in Chrome 52 (Canary) Please confirm that in Comment #5 you are referring to 52.0.2712.0 or later. Navigate to chrome://version to get the full version number.
,
Apr 21 2016
@cmwong: Could you please conform as per the comment #8
,
Apr 21 2016
@rnimmagadda: Yours is the correct behavior. I have further tested mine, but still not successful. (All are using the internal Intel Graphics Display) v52.0.2713.0 ------------ Dev machine 1: Win7, failed (please see attachment) Test machine 2: Win8, failed Test machine 3: Win7, failed v50 --- Dev machine 1: Win7, failed Test machine 2: Win8, failed Test machine 3: Win7, failed v49 --- My colleagues are still using this versions. Some of them show the correct result, others not. Since you can get it work, I suspect it may be a driver problem. Let me try to upgrade the driver firstand try again. Thanks a lot
,
Apr 21 2016
Attachment
,
Apr 21 2016
@cmwong: Could you also please perform the steps mentioned beneath and let us know your observations. 1. Uninstall Google Chrome. 2. Remove the Google Chrome Folder from -> C://Program Files 3. Install Google Chrome Canary Latest Version - 52.0.2713.0 4. Do not Login to Chrome with your credentials. 5. Re-test the same on a clean profile [chrome://settings -> Add Person] Thank you.
,
Apr 21 2016
@rnimmagadda: uninstall all chromes, remove chrome folders in C:\Program Files (x86) and C:\Users\...\AppData, reinstall Chrome v52, no login. Same result. Thanks
,
Apr 21 2016
@junov: Could you please look into this issue.
,
Apr 21 2016
Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 22 2016
,
May 2 2016
Geoff, I think this is a dupe of some GPU clipping issues you were looking at.
,
Jun 15 2016
Just found out that the issue is gone in Version 51.0.2704.84m. Thanks.
,
Jun 15 2016
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by f...@opera.com
, Apr 15 2016