zoid VS x-frame-bypass

See also: https://github.com/krakenjs/zoid which allows you to present a simple interface to sites that want to embed your application and send parameters/register callbacks. All the caveats of frames still apply, of course, and scrolling glitchiness alone is a reason to avoid frames altogether... but if you absolutely need to present your application as a frame, it's a developer-friendly way to do so.

Pdom seems to be a way to do that to yourself, if you can't trust that your content won't cause performance degradations and you absolutely want the context outside that content to stay responsive. I'd only use it, and really any frame, for components where the size is known ahead of time, though; asking a frame to resize itself to fit its contents, when its contents may themselves be resizing to the size of the frame, is a recipe for disaster. Which brings me around to why I try to avoid frames for anything user-facing when at all possible.

IFrames are both terrible and awesome. I built and maintain zoid, which turns iframes into full-fledged components; it's been an adventure: https://github.com/krakenjs/zoid

No idea if it works, but this repo claims to do what you need

You can try this https://github.com/niutech/x-frame-bypass but it may very well not be able to do what you need and chances are it will be a big headache. I'd recommend looking for a different solution.

Try out some queries from your browser history and see if anything beats google. Other engines are more likely to beat google for queries that google has failed at.

Majority of engines were found at below link. Surprisingly many engines use the same indices, for example duckduckgo is mostly just privacy-protected bing. Big thanks to Rohan Kumar.

https://seirdy.one/2021/03/10/search-engines-with-own-indexe...

A proxy is needed to bypass iframe restrictions for most websites. I used this x-frame-bypass client js code [https://github.com/niutech/x-frame-bypass] which (previously?) used proxy.megatunger.com . That free proxy could be recording your queries, who knows, so use caution.

If (when actually) that proxy goes down I think I'll set up something like CORSflare to have a more reliable and trustworthy alternative. [https://github.com/Darkseal/CORSflare]

I hacked this together over about one workday in total so it's likely to have significant issues. You can comment them here or (preferably) file an issue on the repo: [https://github.com/qpwo/searchall/]

There's also a demo video on the repo if the site goes down but you wanted to see how it looks. Feel free to file feature requests on the repo as well. If you'd rather copy it and make your own version then that's fine too.

I'll try to reply to all comments here.