Add documentation page for Popover component

[acelaya]

Depends on #1792

Document the new Popover component introduced in #1791

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (54d82ea) to head (8b15cae).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1793   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           68        68           
  Lines         1220      1220           
  Branches       465       465           
=========================================
  Hits          1220      1220           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[acelaya]

I added this because popovers handled via the popover API are automatically hidden when clicking away, which makes the open state no longer reflect reality.

I didn't notice this first because in the case of Select we have useClickAway, useFocusAway, etc.

I will address this separately, but we'll probably need to add an onClose callback to the Popover and handle a few native events, like toggle one.

[robertknight]

I added this because popovers handled via the popover API are automatically hidden when clicking away, which makes the open state no longer reflect reality.

This seems like an obvious hazard that we should at least document.

I will address this separately, but we'll probably need to add an onClose callback to the Popover and handle a few native events, like toggle one.

Yes, definitely. Is there an issue tracking this?

[acelaya]

Is there an issue tracking this?

Done #1799

[robertknight]

The documentation generally looks good but I notice the examples don't work properly if the native popover API is not available, since there is no positioned container.

[robertknight]

I added this because popovers handled via the popover API are automatically hidden when clicking away, which makes the open state no longer reflect reality.

This seems like an obvious hazard that we should at least document.

I will address this separately, but we'll probably need to add an onClose callback to the Popover and handle a few native events, like toggle one.

Yes, definitely. Is there an issue tracking this?

[acelaya]

I notice the examples don't work properly if the native popover API is not available, since there is no positioned container.

Good catch!