worldcat | WorldCat API for Ruby to interact with WorldCat search | REST library

My suggestion will be put for statement their head class or div.

I haven't checked but this should work:

When you monitor Network traffic [In your browser go to More Tools > Developer Tools > Network or press Ctrl + Shift + I in for chrome browser, and select Network, and filter XHR], you will see that when you click Check Availability, the browser makes a get request to another URL to get the data.

Some issues:

• Adding event listeners within an event listener is in most cases a code smell: this will add those inner listeners each time the outer event is triggered. Those listeners remain attached, and so they accumulate. So, attach all event handlers in the top-level script, i.e. on page load, and then never again.

• The if ... else at the end will execute on page load, and then never again. So the value of menuToggle is guaranteed to be "closed". You need to put that if...else switch inside the handler, so that it executes every time the event triggers, at which time the menuToggle variable will possibly have a modified value.

• The body element does not stretch (by default) over the whole window. If you want to detect a click anywhere on the page, you should attach the listener on the document element itself, not on document.body.

• When the click on the menu placeholder is handled, you should avoid that this event "bubbles" up the DOM tree up to the document, because there you have the other handler that wants to hide the menu again. You can do this with event.stopPropagation().

• The global variable is not absolutely necessary, but if you use it, then I would call it menuVisible and give it a boolean value: false at first, and possibly true later.

• For actually toggling the menu, I would create a function, which takes the desired visibility (false or true) as argument, and then performs the toggle.

• Do not use undeclared variables, like the for loop variable i. Define it with let.

Here is your code with those changes implemented. Of course, there is still a lot that could be improved, but I believe that goes beyond the scope of this question:

You want to remove the dubble quotes (") around your id selector and use :nth-child to select the correct index of the row.

But to be honest, I think you transformed the selector from xPath to literally. You can probably also just do #details tr:nth-child(3) > td (depending on your html structure).