Very limited JavaScript Error Reporting #1508
Description
Hi,
I'm not quite sure if this is the correct place however it seems as on target as it gets.
Over the past few strongs I've received extremely limited JavaScript error reports from my system. The users never get past the security protection. My system sends an error report back to the server but literally all I get is the following:
Uncaught ReferenceError: id is not defined
It reported the error on line "5230" however (script linked below) there is no "id" instance for at least another 11 lines (very common string in my code).
I found you folks based on a Google search (samsung phone development team site:linkedin.com/in/ "browser" "javascript" "engine" -India) which eventually led me to HyukWoo Park's profile where he was gracious enough to mention this project by name.
Here are the three HTTP requests from my Apache access log (note the "SM-G900P Build/LRX21T" substring in the HTTP user agent):
36.148.98.163 - - [06/Nov/2025:01:07:56 +0000] "GET / HTTP/2.0" 202 2341 "-" "Mozilla/5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.1534.1542 Mobile Safari/537.36"
36.148.98.163 - - [06/Nov/2025:01:07:58 +0000] "GET /images/error.jpeg HTTP/2.0" 200 43 "https://www.jabcreations.com/" "Mozilla/5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.1534.1542 Mobile Safari/537.36"
36.148.98.163 - - [06/Nov/2025:01:07:58 +0000] "POST /themes/?ajax=error_javascript HTTP/2.0" 200 38 "https://www.jabcreations.com/" "Mozilla/5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.1534.1542 Mobile Safari/537.36"
My web platform does some rather extensive error tracking. I often joke about knowing if there is a tick on the back of a pig ten miles/kilometers out in the woods because I am hyper-focused on quality. I also want to help other people developing software improve their systems so our overlapping user base can accomplish what they need when you use our respective software platforms.
Two overlapping resources: the window.onerror event handler which my platform uses:
https://developer.mozilla.org/en-US/docs/Web/API/Window/error_event
Also the primary JavaScript file for my platform (you may have to visit the actual website first and then reload the script):
https://www.jabcreations.com/scripts/index.js
On that script simply search for "window.onerror" (there is only one instance). The fifth parameter (error) is much more advanced and my platform supports the older parameters and newer error/fifth parameter. Again, if I'm in the right place I'd be happy to provide direction if it makes someone's day easier. I'd also be happy to setup a Domain Account for free use so anyone working on updating the error reporting has direct access. The JavaScript error reports when they work will make you feel spoiled but more importantly greatly cut down on the guess work saving time.
If this is not the correct project I would greatly appreciate any direct to help the correct team. If it is then I'd be happy to help provide guidance and testing to help make the error reporting part of this JavaScript engine reasonably robust so other developers of platforms and I can keep our software working in the high standards we aspire to. Thank you!