From b9af95a7d3be981ae0a3f6e0abb48c523c734091 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 1 Nov 2025 05:59:43 +0000
Subject: [PATCH 1/2] Initial plan


From fca6ef1e17e87962b45ad8d4299714bb5c185533 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 1 Nov 2025 06:04:53 +0000
Subject: [PATCH 2/2] Add RFC 3986 compliance notes to Uri.Query and
 Uri.Fragment documentation

Co-authored-by: MihaZupan <25307628+MihaZupan@users.noreply.github.com>
---
 xml/System/Uri.xml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/xml/System/Uri.xml b/xml/System/Uri.xml
index 026970f35b2..2a3815d7202 100644
--- a/xml/System/Uri.xml
+++ b/xml/System/Uri.xml
@@ -2108,6 +2108,9 @@ If you used an escaped string to construct this instance (for example, `"http://
 
  The <xref:System.Uri.Fragment%2A> property is not considered in any <xref:System.Uri.Equals%2A> comparison.
 
+ > [!NOTE]
+ > The property includes the leading delimiter (`#`), whereas the URI specification (RFC 3986) recognizes the fragment as the portion of a URI without the delimiter.
+
 ## Examples
  The following example creates a <xref:System.Uri> instance and writes the fragment information to the console.
 
@@ -4218,6 +4221,9 @@ The following examples show a URI and the results of calling <xref:System.Uri.Ge
 
  For more information on IRI support, see the Remarks section for the <xref:System.Uri> class.
 
+ > [!NOTE]
+ > The property includes the leading delimiter (`?`), whereas the URI specification (RFC 3986) recognizes the query as the portion of a URI without the delimiter.
+
 ## Examples
  The following example writes the query `?date=today` to the console.