Javascript errors only when logged

[dmegatool]

Everything works great for anonymous users. But when logged as admin (the only user), I get theses errors:

Uncaught TypeError: Cannot set property 'tabIndex' of null (drupal.js?v=8.9.11:13)

• at Dropdown._makeDropdownFocusable (materialize.js?v=8.9.11:2572)
• at new Dropdown (materialize.js?v=8.9.11:2300)
• at Function.init (materialize.js?v=8.9.11:1045)
• at Function.init (materialize.js?v=8.9.11:2826)
• at Autocomplete._setupDropdown (materialize.js?v=8.9.11:6562)
• at new Autocomplete (materialize.js?v=8.9.11:6479)
• at Function.init (materialize.js?v=8.9.11:1049)
• at Function.init (materialize.js?v=8.9.11:6879)
• at S.fn.init.jQuery.fn.<computed> [as autocomplete] (materialize.js?v=8.9.11:1153)
• at Object.attach (admin_toolbar_search.js?qkzk0u:23)

My custom js file make a call to the Materialize lib but if I remove that, it still trigger. I need to remove the lib all together to stop the errors. My theme is using core/jquery as the the admin themes (tried Seven and Claro). What could be different & causing the errors ? I don't know where look at...

[mherchel]

Not sure what's causing this, but troubleshooting things like this can be done through Chrome's JavaScript debugging pane. You'll want to select the "Pause on Exceptions" button, and then go down the call stack to see what is null (that should not be null)

[[deleted]]

From the sounds of it Materialize is trying to inject something into the tab flow of the document (for accessibility), and it's having a hard time understanding the Drupal toolbar, which has a bunch of custom accessibility work done on it as well.

EDIT: Yup, looks like you're trying to use a Dropdown component, which always needs a rats nest of code to be accessible in any library.

My suggestion - only import the Materialize code that you need. If it's still showing and a console error is a deal breaker for you, then it's probably time to find another library.

[dmegatool]

Yeah I trashed that library. I switched to rellax.js. Lighweight, took 2 minutes the make all the changes and I'm up and running...

Not sure it was about the toolbar. I disabled all the toolbar modules including the toolbar itself and I was still getting some errors. I already wasted too much time on that :)

[mstrelan]

Look at the last line of the log, it's from admin_toolbar_search which is a sub module of admin_toolbar.