"Rendered cell should include style property for positioning" warning when using HOC
See original GitHub issueIf using HOC for a cell being rendered one will get “Rendered cell should include style property for positioning” warnings in console even if style actually set for an inner component. The following example is showing React-Draggable being used together with cell renderer.
...
<Draggable
key={key}
...
<-- we can't put style here because Draggable component doesn't accept such prop
>
<div style={style} ... >
caption
</div>
</Draggable>
...
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:5
Top Results From Across the Web
react-virtualized Grid.cellRenderer - issues adding style prop
I am using the Grid component and have a cellRenderer. In it I attempt to add a backgroundColor style to the outer div....
Read more >Project 18. Positioning
Place elements on the page using relative and absolute positioning. Determine stacking order of elements on the page. Add a background gradient to...
Read more >Hooks FAQ - React
Should I use Hooks, classes, or a mix of both? Do Hooks cover all use cases for classes? Do Hooks replace render props...
Read more >react-virtualized - npm
Start using react-virtualized in your project by running `npm i ... pass through additional properties that affect cell rendering to ensure ...
Read more >title - HTML: HyperText Markup Language - MDN Web Docs
Use the title attribute on an iframe to clearly identify the content of the iframe to ... about document text and may include...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Has anyone discovered a work-around for this? Perhaps we could have a
data-react-virtualized-no-warning
prop that could be used to disable the warning a case-by-case basis?I vote for removing this warning. It is so annoying.