From 19aecc15c51ea4d715960be650ab593817ea834b Mon Sep 17 00:00:00 2001 From: Eric Eastwood Date: Tue, 1 Mar 2022 20:36:28 -0600 Subject: [PATCH] Fix room list being laggy while scrolling MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fix https://github.com/vector-im/element-web/issues/21262 Optimizations: 1. Don't update the `style` (positioning) of hidden tooltips 1. Don't add DOM elements to the page for hidden tooltips > ## Performance problems broken down > > > ### Hidden tooltips rendering on `scroll` > > You can see that the Tooltip render is attached to the `scroll` event at [`src/components/views/elements/Tooltip.tsx#L78-L81`](https://github.com/matrix-org/matrix-react-sdk/blob/31f0a37ca2eeba6a6296787f2fcb33c4b26efebc/src/components/views/elements/Tooltip.tsx#L78-L81) > > The rendering calls [`src/components/views/elements/Tooltip.tsx#L101` -> `updatePosition`](https://github.com/matrix-org/matrix-react-sdk/blob/36adba101caf58afd280e6eedad003b38165be4f/src/components/views/elements/Tooltip.tsx#L101) which ends up as an expensive "Recalculate Style" because it uses [`Element.getBoundingClientRect()`](https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect). This happens many many times within a single `scroll` event. Probably once for each tooltip within the room list **even though no tooltips are event visible as I scroll**. I can see that we're just updating the `style` attribute for a bunch of `.mx_Tooltip_invisible` elements at the end of the document. > > Each one of the purple spans below the `scroll` span ends up as a call to `updatePosition`. And a `scroll` event takes 35ms to 60ms to complete which is way over the 16.6ms 60 FPS budget (on a powerful desktop PC), granted these times are with the performance profiling running. This is without the Passbolt extension explained below. > > And the room list contains about 141 rooms (`document.querySelectorAll('.mx_RoomTile').length`): > > ![](https://user-images.githubusercontent.com/558581/156273551-e744d3d6-93c6-4b07-bb12-6aad361f96a2.png) > > > > ### Passbolt Chrome browser extension exacerbates the problem > > In order to login to Passbolt, it requires a browser extension which defaults to mucking up all pages: > > > > > The extension source seems to be available: https://github.com/passbolt/passbolt_browser_extension > > The Passbolt Chrome extension has a `MutationObserver` listening to all attribute and element changes to the whole `` of the `document` so it can `findAndSetAuthenticationFields` (find form elements and autofill). > > > [`passbolt/passbolt_styleguide` -> `src/react-web-integration/lib/InForm/InFormManager.js#L143`](https://github.com/passbolt/passbolt_styleguide/blob/1c5eddc9102c7cd1029d10dc6836af4722cdba61/src/react-web-integration/lib/InForm/InFormManager.js#L143) > ```js > this.mutationObserver.observe(document.body, { attributes: true, childList: true, subtree: true }); > ``` > > This causes a bunch of `Forced reflow` because the Tooltip `updatePosition` is mutating the element `style` attribute and Passbolt `MutationObserver` callbacks are querying the whole DOM looking for form elements all in the same frame. > > Under the `scroll` event, all of the little spans are the `MutationObserver` -> `findAndSetAuthenticationFields`. With the Passbolt extension, scrolling is verrrrry crunchy and bad. > > ![](https://user-images.githubusercontent.com/558581/156144998-8cf7686f-3c7b-42f8-8d81-ff780bae0ab5.png) > > > #### Workaround > > Instead of running Passbolt on all sites, we can enable the extension to only run on the domain for Passbolt instance itself. I'm guessing the Passbolt extension also does autofill stuff on sites but I always login manually to the Passbolt instance so this solution works for me � > > **Extensions** -> **Passbolt** -> **Details** -> Change **Site access** to `On specific sites` -> Enter in your Passbolt instance `https://passbolt.example.com/` > > ![](https://user-images.githubusercontent.com/558581/156275630-a53ef6a1-c058-4ac9-aa08-ae50b90e72c9.png) > > *-- https://github.com/vector-im/element-web/issues/21262* --- src/components/views/elements/Tooltip.tsx | 11 +++++----- .../views/elements/TooltipTarget.tsx | 22 ++++++++++--------- 2 files changed, 18 insertions(+), 15 deletions(-) diff --git a/src/components/views/elements/Tooltip.tsx b/src/components/views/elements/Tooltip.tsx index 6e7ba994dc7..43af1bc1da3 100644 --- a/src/components/views/elements/Tooltip.tsx +++ b/src/components/views/elements/Tooltip.tsx @@ -98,6 +98,8 @@ export default class Tooltip extends React.Component { }); } + // Add the parent's position to the tooltips, so it's correctly + // positioned, also taking into account any window zoom private updatePosition(style: CSSProperties) { const parentBox = this.parent.getBoundingClientRect(); let offset = 0; @@ -155,11 +157,10 @@ export default class Tooltip extends React.Component { } private renderTooltip = () => { - // Add the parent's position to the tooltips, so it's correctly - // positioned, also taking into account any window zoom - // NOTE: The additional 6 pixels for the left position, is to take account of the - // tooltips chevron - const style = this.updatePosition({}); + let style: CSSProperties = {}; + if(this.props.visible) { + style = this.updatePosition({}); + } // Hide the entire container when not visible. This prevents flashing of the tooltip // if it is not meant to be visible on first mount. style.display = this.props.visible ? "block" : "none"; diff --git a/src/components/views/elements/TooltipTarget.tsx b/src/components/views/elements/TooltipTarget.tsx index 9ccd572ea8a..7dccbae5119 100644 --- a/src/components/views/elements/TooltipTarget.tsx +++ b/src/components/views/elements/TooltipTarget.tsx @@ -44,6 +44,17 @@ const TooltipTarget: React.FC = ({ const show = () => setIsVisible(true); const hide = () => setIsVisible(false); + const tooltip = isVisible && ; + return (
= ({ {...rest} > { children } - + { tooltip }
); };