feat: Partial preserve on refresh

articles/flow/advanced/preserving-state-on-refresh.adoc

@@ -55,16 +55,19 @@
 
 Any elements that aren't direct children of the view component, such as notifications and dialogs, are also preserved. This means that if your `@PreserveOnRefresh` annotated view class opens a dialog in which the user makes edits and then refreshes, the dialog remains visible in its edited state.
 
+=== Partial View Chain Preservation
+
+Partial chain preservation is supported by setting `partialMatch = true` for the [annotationname]`PreserveOnRefresh` annotation.
+This will enable reusing partial chain components from the preserved view chain.
+
+This means that when navigating from a preserve on refresh target to a new url in the same client window context, where windowName matches, the router layouts that have been preserved will be reused without re-creation for the new route.
 
 == Preconditions and Limitations
 
 Using the `@PreserveOnRefresh` annotation has some conditions and limitations. They are as follows:
 
 - The annotation must be placed in a component class that's a route target -- typically annotated with `@Route` -- or on a component that implements [interfacename]`RouterLayout`.
 
-- The annotation doesn't support partial preserving.
-You can't preserve only some components on the route chain. If the annotation is present on any component in the chain, the entire chain is preserved.
-
 - The component is made to persist only when reloaded in the same browser tab -- the `window.name` client-side property is used to identify the tab -- and only if the URL stays the same.
 Visiting another route or changing a URL parameter discards the component state permanently.