8000 Warning: Invalid place prop in Popover causes React DOM warning · Issue #9192 · outline/outline · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Warning: Invalid place prop in Popover causes React DOM warning #9192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
nadia-ben-njima opened this issue May 12, 2025 · 2 comments
Closed
2 tasks done

Comments

@nadia-ben-njima
Copy link
nadia-ben-njima commented May 12, 2025

Is there an existing issue for this?

  • I have searched the existing issues

This is not related to configuring Outline

  • The issue is not related to self-hosting config

Current Behavior

When rendering the Popover component, the following React warning appears in the console:

Warning: Invalid value for prop place on

tag. Either remove it from the element, or pass a string or number value to keep it in the DOM.

This is due to the place prop (coming from the Popover API or internal logic) being spread onto a native

, which does not accept this attribute.

Expected Behavior

There should be no invalid props passed to native DOM elements. The place prop should be filtered out or handled properly before reaching the rendered DOM.

Steps To Reproduce

Click "New document" to start creating a new doc.

Open the browser console.

Observe the warning about the place prop on a

element.

Environment

- Outline:latest
- Browser:Firefox 125

Anything else?

The warning is related to the Popover component. A fix has been made locally by filtering out the invalid place prop before it reaches the DOM.
A pull request has been submitted to address this issue: #9191

Copy link
linear bot commented May 12, 2025

@tommoor
Copy link
Member
tommoor commented May 27, 2025

This will be fixed by #6456

@tommoor tommoor closed this as completed May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0