Skip to content

Commit 7d4b3f8

Browse files
authored
metadata update and review
1 parent cbb9ec1 commit 7d4b3f8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

powerapps-docs/maker/canvas-apps/common-issues-and-resolutions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: powerapps
77
ms.topic: conceptual
88
ms.custom: canvas
99
ms.reviewer:
10-
ms.date: 05/22/2020
10+
ms.date: 06/11/2020
1111
ms.author: kvivek
1212
search.audienceType:
1313
- maker
@@ -22,7 +22,7 @@ This article lists some common issues that you might encounter while using Power
2222
When using embedded canvas apps such as SharePoint forms, SharePoint web parts, and model driven forms, users many see a black box when scrolling covering part of the app. This issue happens with chromium based browsers starting with version 83. There is not a workaround at this time. The team is actively investigating to find a fix and workaround.
2323

2424
1. **Problems downloading attachments in SharePoint custom forms** (May 22, 2020)
25-
When using the attachment control to download an attachment, the click won't have any response when using Google Chrome version 83 or the new Microsoft Edge version 83 browser. As a workaround, change to use the default SharePoint form or use another browser. The team is actively working to fix this issue. **Fix has been deployed weeek of 6/8/2020**
25+
When using the attachment control to download an attachment, the click won't have any response when using Google Chrome version 83 or the new Microsoft Edge version 83 browser. As a workaround, change to use the default SharePoint form or use another browser. The team is actively working to fix this issue. **Fix has been deployed in the weeek of 6/8/2020**
2626

2727
1. **Problems downloading attachments in embedded Power Apps** (May 22, 2020)
2828
When using the attachment control to download an attachment, the click won't have any response when using Google Chrome version 83 or the new Microsoft Edge version 83 browser. As a workaround, use another browser. The team is actively working to fix this issue.

0 commit comments

Comments
 (0)