api2 | Europeana 's Search and Record API | REST library

In your code you are switching into the iframe and accessing an element inside it.
But the submit button is not inside that iframe, so to continue with elements out of that iframe you have to switch to the default content.
This should work better:

Resorting to JSONP is frowned upon nowadays; there are safer alternatives, such as CORS, for cross-origin communication. As the response's content type is application/json, using JSONP will not work anyway because it causes Chrome's CORB feature to kick in.

Why not try to solve whatever CORS issue you seem to be having? I'd be very surprised if the API you're using weren't configured for CORS... A casual inspection of their documentation reveals that you're using the wrong domain, www.gnews.io, instead of gnews.io. The former redirects to the latter, but is not configured for CORS, which explains your CORS troubles.

Once you use the right domain (gnews.io), all your CORS troubles go away. And because there's no longer any need to reach for dirty tricks like JSONP, you can use good old reliable fetch rather than some third-party tool.

The documentation for PDF::Table at https://metacpan.org/pod/PDF::Table#table() suggests that the table() method returns the final Y co-ordinate, so change your code to do my ($final_page, $number_of_pages, $final_y) = $table->table( instead of just $table->table( and your $final_y will tell you where the table ends.

This will also help you to handle the case where the table spans multiple pages.

The duplicate index values in the result can't be explained by the posted code.

In the code:

is there some way to share this package and/or this whole RUN operation across my services in a way so that I can modify this in one place instead?

Yes, you can achieve this by structuring your project as follows:

Since you didn't share a link to that page I can only guess.
So, instead of

Yes, but only because WCAG has added exceptions for the inherent accessibility problems with CAPTCHA. Conformance is not the same as actually working for people with disabilities

It fails at the first hurdle as I can't find a text alternative which is an A level requirement and the first WCAG rule.

Now while that rule does provide for CAPTCHA (so you get a technical pass) it certainly does not fit the spirit of this rule and has always been a point of contention on WCAG.

Providing an audio alternative doesn't work as some people are deaf and blind, which is why a text alternative is a must (a programatically determinable description etc.)

• If you have poor vision there is no way you can differentiate the images.
• If you have a cognitive disability you may not be able to associate the images correctly with the question being asked.
• Using it with a screen reader (as a blind user) is horrendous as you have to use the audio captcha.
• The audio captcha is useless if you also have a hearing impairment (it is hard to use even if you don't).
• Using it with a braille screen (if you are blind and deaf for example) is impossible.

I could go on, but you get the idea. Especially that last point. Yes Google provides alternatives to "tick the boxes" but neither option is useful for someone who is blind and deaf.

Not really, you can buy 1,000 captcha solves for $5!.

All you are actually doing is helping Google perfect self driving cars image recognition when you implement a Captcha (why do you think they show you pictures of buses) and annoy your visitors.

In the mean time you are

• introducing friction for users who want to fill out your form (and depending on usage could result in a lower conversion rate),
• making the site hard or impossible to use for disabled users
• probably making your site slower (depending on implementation) as the Captcha library is bloated, hurting your Core Web Vitals.

Avoid and do not use!

I believe your goal is as follows.

• You want to retrieve the 1st values from the URL of https://pool.rplant.xyz/api2/poolminer2x/raptoreum/RThRfoQJg8qsoStLk7QdThQGmpbFUCtvnk/UlRoUmZvUUpnOHFzb1N0TGs3UWRUaFFHbXBiRlVDdHZua3x4 using Google Apps Script and want to use the retrieved values at Google Spreadsheet.

When I saw https://github.com/amvtek/EventSource/blob/master/dist/eventsource.js, it seems that the request is run with XMLHttpRequest. At Google Apps Script, UrlFetchApp is used, and XMLHttpRequest cannot be used. I thought that this might be the reason for your current issue. But unfortunately, in the current stage, this cannot use text/event-stream type at Google Apps Script. When your URL is requested with UrlFetchApp, it looks like the infinite loop. This is the current situation.

So, from My goal is just to retrieve one response from the endpoint though, so any way I can accomplish that in Google Sheets would be great. and the above situation, I would like to propose a workaround. When you are running your script on Google Spreadsheet, how about retrieving the value from the URL using Javascript? Google Apps Script can retrieve the values from Javascript side using a dialog and a sidebar. From your question, when Javascript is used, the value can be retrieved. I thought that this might be able to be used. When this workaround is reflected in the Google Apps Script, it is as follows.

Please copy and paste the following script to the script file of the script editor of Google Spreadsheet.