You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WithTooltip component uses react-popper-tooltip, which depends on the rather bulky (and dated) Popperjs library. We should be able to reduce the bundle size of @storybook/core/components by moving to @radix/tooltip-react or something similar. This also follows our general goal of improving a11y by moving to Radix UI.
We should also look into the alternative of using Floating UI directly - either via @floating-ui/react or @floating-ui/react-dom. This should be even smaller but might come at the cost of a11y which wouldn't be the right trade off IMO. Radix UI uses Floating UI internally. Floating UI is the spiritual successor to Popperjs, built by the same people.
Something similar was already attempted in #24496 by @danielmarcano (for a11y reasons), but ended up being abandoned because of lack of prioritisation from the team AFAIK.
The
WithTooltip
component usesreact-popper-tooltip
, which depends on the rather bulky (and dated) Popperjs library. We should be able to reduce the bundle size of@storybook/core/components
by moving to@radix/tooltip-react
or something similar. This also follows our general goal of improving a11y by moving to Radix UI.We should also look into the alternative of using Floating UI directly - either via
@floating-ui/react
or@floating-ui/react-dom
. This should be even smaller but might come at the cost of a11y which wouldn't be the right trade off IMO. Radix UI uses Floating UI internally. Floating UI is the spiritual successor to Popperjs, built by the same people.Something similar was already attempted in #24496 by @danielmarcano (for a11y reasons), but ended up being abandoned because of lack of prioritisation from the team AFAIK.
https://635781f3500dd2c49e189caf-rjflqvpgls.chromatic.com/?path=/story/bench--es-build-analyzer&args=metafile:core_SLASH_components_DOT_esm_DOT_json
The text was updated successfully, but these errors were encountered: