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.
Cannot read property 'offset' of null
See original GitHub issueWhile using ctrl+shift+F12 or ctrl+hover on the class/id of an html element, getting the error :
Cannot read property ‘offset’ of null
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:8 (5 by maintainers)
Top Results From Across the Web
TypeError: Cannot read property 'offsetHeight' of Null in JS
The "Cannot read property 'offsetHeight' of null" error occurs when trying to access the offsetHeight property on a null value. To solve the...
Read more >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 >Uncaught TypeError: Cannot read property 'offsetWidth' of null
Uncaught TypeError : Cannot read property 'offsetWidth' of null ... I am using a child theme so I think this is the problem...
Read more >#9040 ("Uncaught TypeError: Cannot read property 'left' of null ...
The droppable "refreshPositions" method will try to re-calculate positions for all items, even for the removed ones, and jQuery will break with an...
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 have a fix that makes it so this issue doesn’t cancel all symbols and instead only prevents symbols from the affected file. I plan to ship it in the next version (2.1.1)
Thank you for the crash example repo @VitalyName I was able to recreate a simple example of that issue happening and narrowed it down as stemming from
vscode-css-langaugeservice.I’ve opened up an upstream issue about this here: https://github.com/Microsoft/vscode-css-languageservice/issues/83 and will update the dep in my project once it’s fixed there