Context Menu Demo not working

[adam-bentley]

Bug Report

Steps

1. Go to the semantic ui react documentation site.
   https://react.semantic-ui.com/modules/popup/#usage-context-menu
2. Scroll down to the context menu.
3. Try and right-click to open the context menu and it won't show anything.
4. Click sandbox.
5. Try and right-click to open the context menu and it will error.

Expected Result

A context menu to appear.

Actual Result

Nothing || error stack trace.

×
TypeError
Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.
    at getComputedStyle (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/dom-utils/getComputedStyle.js:8:42
    at getClippingParents (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/dom-utils/getClippingRect.js:47:86
    at getClippingRect (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/dom-utils/getClippingRect.js:57:62
    at detectOverflow (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/utils/detectOverflow.js:30:56
    at hide (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/modifiers/hide.js:32:54
    at Object.forceUpdate (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/createPopper.js:109:21
    at eval (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/createPopper.js:120:20
    at eval (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/createPopper.js:119:16
    at eval (https://sgc5zn.csb.app/node_modules/
popperjs/core/lib/utils/debounce.js:12:19
This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error.
This error overlay is powered by `react-error-overlay` used in `create-react-app`.

Version

3.0.0-beta2

[maximal01]

I had to rollback to v2.1.4 to solve this issue.

[adam-bentley]

This is still broken on the website, any update?

[replaysMike]

just hit this as well

[cristian-spiescu]

I think this regression was introduced in v2.1.5. Our code works well w/ v2.1.4, but throws a similar error w/ v2.1.5