From 0582fe6a9f89b94232ab985e3fee24bc01652310 Mon Sep 17 00:00:00 2001 From: Arlo Date: Wed, 9 Feb 2022 00:08:08 +0000 Subject: [PATCH] Fixed #605 --- docs/extensions/FrameworkElementExtensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extensions/FrameworkElementExtensions.md b/docs/extensions/FrameworkElementExtensions.md index ae163f325..9f333cf86 100644 --- a/docs/extensions/FrameworkElementExtensions.md +++ b/docs/extensions/FrameworkElementExtensions.md @@ -126,7 +126,7 @@ Here is how you can easily set a custom cursor type for a target `FrameworkEleme ``` > [!NOTE] -> Even though Microsoft recommends in [UWP Design guidelines](/uwp/input-and-devices/mouse-interactions#cursors) hover effects instead of custom cursors over interactive elements, custom cursors can be useful in some specific scenarios. +> Even though Microsoft recommends in [UWP Design guidelines](/windows/apps/design/input/mouse-interactions#cursors) hover effects instead of custom cursors over interactive elements, custom cursors can be useful in some specific scenarios. > [!WARNING] > Because the UWP framework does not support metadata on attached properties, specifically the [`FrameworkPropertyMetadata.Inherits`](/dotnet/api/system.windows.frameworkpropertymetadata.-ctor#System_Windows_FrameworkPropertyMetadata__ctor_System_Object_System_Windows_FrameworkPropertyMetadataOptions_System_Windows_PropertyChangedCallback_System_Windows_CoerceValueCallback_) flag, the `Cursor` property might not work properly in some very specific XAML layout scenarios when combining nested `FrameworkElement`-s with different `CoreCursorType` values set on them.