## background When some js functions do not work as expected, this article tries to give a debug solution to pinpoint the problem. ## Web inspector (DevTools) GoldenDict-ng has embedded an inspector, which is actually [chromium's DevTools](https://developer.chrome.com/docs/devtools). You can trigger it manually using `F12`. Screenshot: ![Inspector](../img/inspector.png) ## Navigate to the specified element Click the find element and move the mouse to the specified element, click the element will navigate the source panel to the very place. ![steps](../img/inspector-steps.png) ## Modify the CSS style you can play around with the CSS to modify the appearance of the HTML and check the results. ![style](../img/inspector-style.png) ## Check javascript events - navigate to the specified element - check the "Event Listeners" panel - pay attention to the click events - in the following screenshot, there are two registered event listeners, one from the goldendict `gd-custom.js` and one from the HTML itself. - click the above event listener location will locate to the right place in the JavaScript. ![event](../img/inspector-event.png) If some desired event does not trigger, it can first check do the event listeners have been successfully registered. Then set a breakpoint in the right place to check whether the event has been triggered and if it can execute successfully. ![breakpoint](../img/inspector-breakpoint.png) ## Reproduce the issues following your normal operations and debugging the JavaScript code and pay attention to the console output. Whether any errors happened. ![Alt text](../img/inspector-console.png)