[css-navigation-1] Move the section on the url-pattern() function.

This moves the section for the url-pattern() function into the newly
created umbrella section on defining URL patterns.

Author: dbaron

css-navigation-1/Overview.bs

@@ -129,6 +129,67 @@ NOTE: The bracing syntax also allows for future expansion if needed.
 NOTE: Some of the design discussion for this feature has been in
 <a href="https://github.com/w3c/csswg-drafts/issues/12594">w3c/csswg-drafts#12594</a>.
 
+<h3 id="url-pattern-function">The ''url-pattern()'' function</h3>
+
+<!--
+
+NOTE: We may eventually want to move this to css-values.
+
+If we do, the definition of "style resource base URL" probably doesn't need to be
+exported any more, since it was exported for this definition.
+
+-->
+
+The <dfn export function>url-pattern()</dfn> function represents a [=URL pattern=],
+which can be used to match URLs.
+
+<pre class="prod def">
+<<url-pattern()>> = url-pattern( <<string>> )
+</pre>
+
+This function represents a [=URL pattern=] that can be created
+using the steps of the <dfn>create a URL pattern for url-pattern()</dfn> algorithm:
+
+1. Let <var>arg</var> be the <<string>> argument to the ''url-pattern()'' function.
+
+1. Let <var>baseURL</var> be the [=style resource base URL=] of
+    the rule or declaration block containing the ''url-pattern()'' function.
+
+    <div class="issue">
+    Do we want this to be the base URL all the time?
+    For use of ''url-pattern()'' in ''@navigation'',
+    it's likely more useful for the base URL
+    to be the document URL rather than the style sheet URL.
+    However, it would be very awkward for ''url-pattern()''
+    to be inconsistent with ''url()''.
+
+    Should we allow the base URL of ''url-pattern()''
+    to be defined by the consumer?
+    Should we introduce <code>document-url-pattern()</code>?
+    Should we do something similar to
+    [[css-images-3#ambiguous-urls]]
+    (see <w3c/csswg-drafts#383>)?
+
+    Also see other proposed uses of {{URLPattern}} in CSS
+    in <w3c/csswg-drafts#10975>,
+    for '':local-link''.
+    </div>
+
+1. Return the result of [=URL pattern/create|create a URL pattern=] given
+    <var>arg</var>, <var>baseURL</var>, and an empty [=map=].
+
+NOTE: This function requires that its argument is quoted.
+This differs from the ''url()'' function,
+which allows its argument to be quoted or unquoted.
+
+To <dfn export>serialize a ''url-pattern()'' function</dfn> <var>f</var>,
+[=serialize a function=] <var>f</var>,
+using [=serialize a string=] on the single argument
+to serialize <var>f</var>'s contents.
+
+NOTE: This is defined this way because {{URLPattern}}
+intentionally does not provide a serialization.
+
 <h3 id="route-value-type">The <<route-location>> value type</h3>
 
 <pre class="prod def" dfn-type="type" nohighlight>
@@ -729,67 +790,6 @@ and other things where this section links to non-exported definitions.
 ISSUE: Generally figure out if these definitions should care about
 the [=ongoing navigate event=] or the [=transition=].
 
-<h2 id="url-pattern-function">The ''url-pattern()'' function</h2>
-
-<!--
-
-NOTE: We may eventually want to move this to css-values.
-
-If we do, the definition of "style resource base URL" probably doesn't need to be
-exported any more, since it was exported for this definition.
-
--->
-
-The <dfn export function>url-pattern()</dfn> function represents a [=URL pattern=],
-which can be used to match URLs.
-
-<pre class="prod def">
-<<url-pattern()>> = url-pattern( <<string>> )
-</pre>
-
-This function represents a [=URL pattern=] that can be created
-using the steps of the <dfn>create a URL pattern for url-pattern()</dfn> algorithm:
-
-1. Let <var>arg</var> be the <<string>> argument to the ''url-pattern()'' function.
-
-1. Let <var>baseURL</var> be the [=style resource base URL=] of
-    the rule or declaration block containing the ''url-pattern()'' function.
-
-    <div class="issue">
-    Do we want this to be the base URL all the time?
-    For use of ''url-pattern()'' in ''@navigation'',
-    it's likely more useful for the base URL
-    to be the document URL rather than the style sheet URL.
-    However, it would be very awkward for ''url-pattern()''
-    to be inconsistent with ''url()''.
-
-    Should we allow the base URL of ''url-pattern()''
-    to be defined by the consumer?
-    Should we introduce <code>document-url-pattern()</code>?
-    Should we do something similar to
-    [[css-images-3#ambiguous-urls]]
-    (see <w3c/csswg-drafts#383>)?
-
-    Also see other proposed uses of {{URLPattern}} in CSS
-    in <w3c/csswg-drafts#10975>,
-    for '':local-link''.
-    </div>
-
-1. Return the result of [=URL pattern/create|create a URL pattern=] given
-    <var>arg</var>, <var>baseURL</var>, and an empty [=map=].
-
-NOTE: This function requires that its argument is quoted.
-This differs from the ''url()'' function,
-which allows its argument to be quoted or unquoted.
-
-To <dfn export>serialize a ''url-pattern()'' function</dfn> <var>f</var>,
-[=serialize a function=] <var>f</var>,
-using [=serialize a string=] on the single argument
-to serialize <var>f</var>'s contents.
-
-NOTE: This is defined this way because {{URLPattern}}
-intentionally does not provide a serialization.
-
 <h2 class="no-num" id="privacy">Privacy Considerations</h2>
 
 ISSUE: To be written.