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
Popovers, Menus, Selects, Comboxes, and Tooltips currently always render a portal + display: 'none' elements in the DOM. Here's an example in a LifeOmic app with a TableModule and tooltips for multiple actions.
As you can see from the image, some of this is the due to the way Reakit works with portals. Maybe we shouldn't portal as much or should cut back on what we do portal?
Options
Question: Do we need portals on all of these components?
Upgrade to latest version of Reakit and see if there are any improvements in this area. Maybe we are doing something wrong / not recommended as well? May be good to start a GitHub issue or a Spectrum chat about this.
Find another a11y solution for these types of elements that don't clutter the DOM with invisible elements and only renders them when they are displayed. The benefit of using Reakit is due to the a11y bits it provides
Open to other options as well, as long as we can retain the a11y (WAI-ARIA) standards
The text was updated successfully, but these errors were encountered:
Summary
Popovers, Menus, Selects, Comboxes, and Tooltips currently always render a portal +
display: 'none'
elements in the DOM. Here's an example in a LifeOmic app with a TableModule and tooltips for multiple actions.As you can see from the image, some of this is the due to the way Reakit works with portals. Maybe we shouldn't portal as much or should cut back on what we do portal?
Options
The text was updated successfully, but these errors were encountered: