Bug 36811 - JS error on all staff interface and OPAC pages - Uncaught TypeError Cannot read properties of null
Summary: JS error on all staff interface and OPAC pages - Uncaught TypeError Cannot re...
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-08 11:13 UTC by David Nind
Modified: 2024-10-29 22:48 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Error message - Chromium browser (72.47 KB, image/png)
2024-05-15 18:41 UTC, David Nind 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Nind 2024-05-08 11:13:31 UTC 
This JavaScript error appears on every page in the OPAC and staff interface:

Uncaught TypeError: Cannot read properties of null (reading 'addEventListener')
    at share-modal.js:1:135

To replicate:
1. Enable the developer tools for your browser.
2. View several pages in the staff interface and OPAC.
3. Notice the JS error on every page.
Comment 1 Brendan Lawlor 2024-05-15 14:42:30 UTC 
Is this still valid? I can't reproduce in either the staff interface or OPAC.

I tried many different pages, saw some warnings about markup, but no js error.
Comment 2 Katrin Fischer 2024-05-15 16:05:17 UTC 
Same for me.
Comment 3 David Nind 2024-05-15 18:41:38 UTC 
Created attachment 166789 [details]
Error message - Chromium browser

I've re-checked.

This only shows when using the Chromium browser (v124.0.6367.155).

It doesn't show when using Firefox or Google Chrome.

Will change status.
Comment 4 Katrin Fischer 2024-05-16 07:15:45 UTC 
Thanks David, I was testing in Firefox.
Comment 5 David Nind 2024-10-29 22:48:52 UTC 
No longer seeing this, so must have been fixed by "something else".