using overflow: auto or scroll, List needs to listen for scroll events on that element instead. On initialization, List will traverse up the DOM looking for the first element with the data-is-scrollable attribute to know which element to listen to for knowing when to re-evaulate the visible window.
+By default, the List will use the \if{html}{\out{}} element as the scrollable element. If you contain List within a scrollable \if{html}{\out{
}} using overflow: auto or scroll, List needs to listen for scroll events on that element instead. On initialization, List will traverse up the DOM looking for the first element with the data-is-scrollable attribute to know which element to listen to for knowing when to re-evaulate the visible window.
}
\subsection{My list isn't re-rendering when I mutate its items, what should I do?}{
To determine if List should re-render its contents, the component performs a referential equality check on the items array in its shouldComponentUpdate method. This is done to minimize the performance overhead associating with re-rendering the virtualized list pages, as recommended by the React documentation.
-As a result of this implementation, List will not determine it should re-render if values within the array are mutated. To avoid this problem, we recommend re-creating the items array using a method such as Array.prototype.concat or ES6 spread syntax shown below:\preformatted{public appendItems(): void \{
+As a result of this implementation, List will not determine it should re-render if values within the array are mutated. To avoid this problem, we recommend re-creating the items array using a method such as Array.prototype.concat or ES6 spread syntax shown below:
+
+\if{html}{\out{
}}\preformatted{public appendItems(): void \{
const \{ items \} = this.state;
this.setState(\{
@@ -94,7 +96,7 @@ public render(): JSX.Element \{
return
;
\}
-}
+}\if{html}{\out{
}}
Since the items array has been re-created, the list will conclude that its contents have changed and it should re-render the new values.
}
diff --git a/man/SearchBox.Rd b/man/SearchBox.Rd
index 354182ac..0dcfcd0c 100644
--- a/man/SearchBox.Rd
+++ b/man/SearchBox.Rd
@@ -66,7 +66,7 @@ you need to work using the original docs to achieve the desired result.
\subsection{Content}{
\itemize{
\item Use placeholder text in the search box to describe what people can search for. For example, "Search", "Search files", or "Search contacts list".
-\item Although search entry points tend to be similarly visualized, they can provide access to results that range from broad to narrow. By effectively communicating the scope of a search, you can ensure that people's expectations are met by the capabilities of the search you're performing, which will reduce the possibility of frustration. The search entry point should be placed near the content being searched.
Some common search scopes include:
+\item Although search entry points tend to be similarly visualized, they can provide access to results that range from broad to narrow. By effectively communicating the scope of a search, you can ensure that people's expectations are met by the capabilities of the search you're performing, which will reduce the possibility of frustration. The search entry point should be placed near the content being searched.\if{html}{\out{
}}\if{html}{\out{
}}Some common search scopes include:
\itemize{
\item \strong{Global}: Search across multiple sources of cloud and local content. Varied results include URLs, documents, media, actions, apps, and more.
\item \strong{Web}: Search a web index. Results include pages, entities, and answers.
+# shiny.fluent 
-Appsilon is the **Full Service Certified RStudio Partner**. Learn more
-at [appsilon.com](https://appsilon.com).
+Appsilon is a **Posit (formerly RStudio) Full Service Certified Partner**.