Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Uncaught TypeError: Cannot read property 'offsetTop' of null
See original GitHub issueHi i’m trying to use this module in a meteor 1.2 project, but when i click the component for select an option,i get the following error message.
Select.js:193 Uncaught TypeError: Cannot read property 'offsetTop' of null
I used the example code for test in my project.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Uncaught TypeError: Cannot read property 'offsetTop' of null
Currently you are trying to access the element with the id myTopnav when the browser hasn't parsed the HTML yet, which means your...
Read more >Uncaught TypeError: Cannot read property 'offsetTop' of null #14
I'm getting multiple console errors saying 'Uncaught TypeError: Cannot read property 'offsetTop' of null'. Is there a fix for this?
Read more >Type error: Cannot read property offsetTop of null react ...
Coding example for the question Type error: Cannot read property offsetTop of null react. Unmounted component-Reactjs.
Read more >HTMLElement.offsetTop - Web APIs | MDN
The HTMLElement.offsetTop read-only property returns the distance of the outer border of the current element relative to the inner border of ...
Read more >cannot read properties of null (reading 'click') react - You.com
In your html there is no element with id j1_64_anchor . So your code document.getElementById('j1_64_anchor').click(); will fail.
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
I experienced this issue when deving a symlinked library that had an old version of react-dom. The library was running 15, but the main project was 16. It’s not super relevant to the actual bug but I was able to fix the error by upgrading the library. Just posting here as the error was a little confusing and google landed me here.
Any update on this issue, we are experiencing the same problem