[Question] Pop-out/floating tab throws "Cannot read property getBoundingClientRect of null"
See original GitHub issueHello, I’m trying to use the poput/floating window. It doesn’t seem to matter, but I’m triggering it like this, after ensuring there’s at least 1 tab node:
model.doAction(Actions.floatTab((tabSet.getSelectedNode() as TabNode).getId()));
What I get is a quick render flash (that looks like the right component), then an error (sadly can’t copy paste the text):
Could you provide any pointers on why this might be happening? Are there any conditions the tab-components should meet?
Thank you
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Tabs: "Cannot read property 'getBoundingClientRect' of null"
Problem Reliably getting an error with HMR updates:Uncaught TypeError: Cannot read property 'getBoundingClientRect' of null at Tabs.js:86 ...
Read more >Cannot read property 'getBoundingClientRect' of null
As I noticed your code, there you used arrow function with componentDidMount. It should be: componentDidMount() {}.
Read more >Throwing Cannot read property 'getBoundingClientRect' of ...
I went and looked inside the scroll plugin and found that it had a method _unwrapElement or something like this that could return...
Read more >Popup: Cannot read property 'getBoundingClientRect' of null
The popup that opens from the main page in the sample opens correctly. The popup that is supposed to open from the dialog...
Read more >TypeError: Cannot read property 'getBoundingClientRect' of null
Description of the problem: Cannot type anything in the text box on Pavlovia but works perfectly fine in desktop Error message: TypeError: Cannot...
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 Free
Top 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
FloatingWindowTab does have an error boundary
The popout windows use portals, see: https://medium.com/hackernoon/using-a-react-16-portal-to-do-something-cool-2a2d627b0202
It does indeed, that’s where we got the idea to include this feature 😃 Do you have any error boundaries or catches that could maybe hide if our code throws? I’m gonna spend more time debugging this and let you know if I find the solution. Any pointers on where you’d start is appreciated!