adding preserve-view=true

Author: sloanster

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/ask-device-permission-api-takes-too-long.md

@@ -13,18 +13,18 @@ ms.subservice: calling
 ---
 
 # The askDevicePermission API takes too long
-The [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API will have the end user will be shown a browser prompt asking if they allow permission to use (camera or microphone).
+The [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API will have the end user will be shown a browser prompt asking if they allow permission to use (camera or microphone).
 If the end users aproves to use their camera or microphone then those devices will be available to be used in a call and their availability will be reflected in available device list.
 If you find that this API is taking a long time to respond, it could be due to delays in the end user approving the permission prompt user interface.
 
 Occasionally, the device list update step can take a long time.
 This issue is usually because the driver layer responds late, which can happen with some virtual audio devices in particular. [Chromium Issue 1402866](https://bugs.chromium.org/p/chromium/issues/detail?id=1402866&no_tracker_redirect=1)
 
 ## How to detect using the SDK
-To detect this issue, you can measure the time difference between when you call the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API and when the promise resolves or rejects.
+To detect this issue, you can measure the time difference between when you call the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API and when the promise resolves or rejects.
 
 ## How to mitigate or resolve
-If the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API fails due to the user not responding to the permission prompt UI,
+If the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API fails due to the user not responding to the permission prompt UI,
 the application can retry the API again and the user should see the permission prompt UI.
 
 If the device list update step takes a long time, the user should check their audio device list and see if there's any device that could potentially be causing this issue.

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/no-permission-prompt.md

@@ -25,7 +25,7 @@ causing the browser to skip the prompt even if the permission state is set to `p
 We can't detect whether the permission prompt actually shows or not, as this browser behavior can't be detected at JavaScript layer.
 
 ## How to mitigate or resolve
-The application should check the result of [`DeviceManager.askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API.
+The application should check the result of [`DeviceManager.askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API.
 If the result is false, it may indicate that user denied the permission now or previously.
 
 The application should show a warning message and ask the user to check their browser settings to ensure that correct permissions have been granted.