blue-button | Blue Button to JSON Parser | JSON Processing library

Don't repeat JavsScript code. Instead delegate a click to every .button-container's img element:

To remove the attribute disabled="" you can use the following line of code:

As Chris G has mentioned, id attributes are meant to be unique to that specific element.

MDN Web Docs describes an id attribute as the following:

The id global attribute defines an identifier (ID) which must be unique in the whole document. Its purpose is to identify the element when linking (using a fragment identifier), scripting, or styling (with CSS).

Don't use onClick(), but simply change the ids to something more descriptive that are unique. It also makes finding specific elements in your code much easier.

If you cannot change the code, for example if you are web scraping and need them elements, you can use .modal-button:nth-child() to find whatever button you need.

Events won't automatically propagate up when you wrap a component.

You'd either need to pass them on individually, something like this:

Disclaimer: these are a few of what I think of as "best practices." Others may disagree; YMMV. Also this is assuming you don't want to use libraries or frameworks like Vue.js or React.js, which in general will do things quite differently. Depending on circumstances these libraries can have both advantages and drawbacks.

But within those limits, the general idea is this:

• Keep the event handler generic, so that one function can do multiple things.
• Pass in stuff that differs between links as attributes. This keeps things related to the activity together at the link.
• I like to attach the event listener higher up in the DOM and then handle the events as they bubble. In this case we're attaching the event to the ul tag, and catching any click events that bubble up from a tags. IMHO this has a few advantages:
  • if you mutate the list, new links will automatically use the current event handler.
  • you only have one event handler attached to the DOM, instead of 3 (however many a tags you have)
  • this also gives you the chance to add other event listeners directly to specific a tags if you want to do something special before (or instead of) the default action. Because events attached directly happen first, and then the event bubbles. If you want it to happen instead of, you would just call e.stopPropagation() to prevent the event from bubbling.

Also what I've done sometimes in the past is to have a single generic page with header and navbar, and then load the main content div via ajax. This has the very visually pleasing effect that when you go to a different page the navbar stays put, and doesn't reload. You could easily do this in the example code below, if changePage was doing an XHR/fetch, and then loading the contents into a main content div.

In this greatly simplified example, I show how we can use the href, innerText, and a data attribute to do different things depending on which link is clicked. Of course you can do as much (or as little) as you want/need in this regard.

A work-around is to add the two lines following // correct PMA BTABLE to HAL_PCD_EP_Transmit() in stm32f3xx_hal_pcd.c:

You need to send a response in your sendMail call, otherwise your browser never receives anything. Try this:

The routerLink directive applied to an a element sets an href attribute upon this element.

I guess the same exception is thrown on click but the event still bubbles up and then the default behavior is executed and the page location is changed. As this happens really fast, you don't notice the error.

Try preserving the console logs even after page relaod, the error should be there.

If error continues , try change tag to tag and check .

Maybe this.setState in function changeSelector in child component wrong you must change like follow.