445: Uncaught TypeError

Post

Posted
Rating:
#2678 (In Topic #529)
So, I keep getting the following fun error popup...

Fun Error Popup said


An error occurred when loading this screen onto the web browser. You are being notified of this as you are staff. If you believe this is a bug in Composr, please contact the developers with full details. More details are available in your browser's error console. The error was:

445: Uncaught TypeError: Cannot read property 'getBoundingClientRect' of null
https://legendsofnorova.net/themes/Ablution/templates_cached/EN/global_ssl.js?1493481087

Post

Posted
Rating:
#2682
Are you able to find a stack trace for this? If you have your browser error console open when it happens, it usually will print a full stack trace in there.

Post

Posted
Rating:
#2683
Also what browser, and any specific page and situation it happens on?

Post

Posted
Rating:
#2684
This should suppress it, but I'd like to know the true cause. Only a stack trace will tell me, as this is a very commonly used function.
https://github.com/ocproducts/composr/commit/9a23d4c20266dafb5ae9bc1a55fb9267b74d9792

Post

Posted
Rating:
#2700
Sorry, got busy. I don't want to suppress it, thanks though. I rather catch it and have it fixed. Luckily I'm the only one to see it.

I use Vivaldi. The error console only gives me this:

Code

[Violation] Forced reflow while executing JavaScript took 138ms
[Violation] Forced reflow while executing JavaScript took 130ms
global_ssl.js?1493481087:445 Uncaught TypeError: Cannot read property 'getBoundingClientRect' of null
    at find_pos_y (global_ssl.js?1493481087:445)
    at internalise_ajax_block_wrapper_links (ajax_ssl.js?1493481087:47)
    at index.php?page=start:2984
find_pos_y @ global_ssl.js?1493481087:445
internalise_ajax_block_wrapper_links @ ajax_ssl.js?1493481087:47
(anonymous) @ index.php?page=start:2984
index.php?page=start:2983 [Violation] 'setTimeout' handler took 80ms
browser-bundle.js:2 [Violation] 'requestIdleCallback' handler took 55ms
browser-bundle.js:2 [Violation] 'setTimeout' handler took 446ms

This happens anywhere. Just loading the site or refreshing the page is enough to make it happen.

Post

Posted
Rating:
#2702
Fixed :)
1 guest and 0 members have recently viewed this.