A table may be divided each row into separate cells

Something is very strange with that sentence :P It's not proper grammar, but more than that I don't understand what is trying to be said either.

I think a better "point of view" can be omitted for better reading because everyone knows what you are talking about, which the sample code might not compatible on their machines or browsers

Website is wider and therefore (especially on small screens) there is a white strip and horizontal scrollbar. See screenshot below

Bug description:

Accordion Custom header demo does not follow WAI-ARIA Authoring Practices for accordion.

The title of each accordion header is contained in an element with role button.
Each accordion header button is wrapped in

Switching to bodyMode left our tooltips non functional, since in svg e.g. a textbox often is composed of a , but the tooltip should popup everywhere inside the g, e.g.
<g data-tip="my tip"><rect/><text/></g>
But body mode will currently search the data-tip in rect if you click on the box with no text or if you click on text.

bodyListener should search from e.tar

I created a dev.to post on a dropdown component where it uses the new recommended hook usePopper and I had an awfully hard time getting the example on the docs to work. If I was to PR some additions to the docs with a dropdown example, would that be accepted?

[Code sandbox](https://codesandbox.io/s/3-react-pop

Appreciate all the hard work on this project, but it would be nice to have more explicit/verbose documentation on the use of the various v-popover props. As it stands, I can't successfully position the v-popover using any of the props. The only one that seems to have any effect is :offset which results in wild and random page placement. I'm 99.99999% sure I'm missing something, but it would b

A documentation on how close policy works is required. Where may I find it?
Especially, I want to know what does the consume boolean means and does?

The tooltip is shown on hover, but remains active on focus too. So when clicking a button with tooltip, the tooltip will remain active until i click somewhere else. I think the default behaviour should be to remove the tooltip after hovering out, and leave the current behaviour as optional, to be activated via a custom attribute.

Can I bring up the popup in response to a click of the right mouse button?

It looks like this is not possible, please consider this a feature request. :-) Thanks!

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-describedby_attribute

The aria-describedby attribute is used to indicate the IDs of the elements that describe the object. It is used to establish a relationship between widgets or groups and text that described them. This is very similar to aria-labelledby: a label describes the essence of an object,

Just a suggestion based upon a gotcha I encountered. When using SSR you get 'document is not defined' (since document is client side only). I modified your example to remedy this.

  const { Portal } = usePortal({
    bindTo: typeof window !== 'undefined' ? document && document.getElementById('selector') : null
  })

Thanks for the package.

Would appreciate a quick summary of browser support for each component in the Readme. A bit like what you did in this pen: http://codepen.io/LFeh/pen/oEula

Hi!

Please look at the example https://stackblitz.com/edit/react-t211ct

Make sure your window is narrower than that number container (500px or less). Then scroll to the right and hover over rightmost numbers. The body width equals window width, but the tooltip container is wider than the body.

I hotfixed the bug in my project by updating the if