Holiday Notice: Support will be provided on a limited scale from December 24th, 2024, to January 2nd, 2025. Happy holidays and a wonderful New Year!


Topic: Scrollspy throws a TypeError due to ref.current being null

Stoofie free asked 2 years ago


Expected behavior

Not throw a TypeError and be able to handle cases where current is still null.

Actual behavior

Throws a TypeError cannot read properties of null (reading 'offsetTop').

Resources (screenshots, code snippets etc.) enter image description here

Not sure if this is an issue on my side but we have dynamic scrollspy sections being rendered and thus I've created an array of refs to handle the targets & subsections.

Example code as follow:

enter image description here This is how I map the array of refs onto the scrollspy components: enter image description here

Debugging the component's render I can see the .current for the refs are null, however they are changed later on by the components containing the refs as follow: enter image description here Seeing as refs do not trigger a re-render, how can I get pass this issue?


Wojciech Staniszewski staff commented 2 years ago

You could try to store the reference to the element in the useState hook. It will trigger rerender.



Please insert min. 20 characters.

FREE CONSULTATION

Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.

Status

Opened

Specification of the issue

  • ForumUser: Free
  • Premium support: No
  • Technology: MDB React
  • MDB Version: MDB5 4.0.0
  • Device: N/A
  • Browser: Chrome
  • OS: Windows
  • Provided sample code: No
  • Provided link: No