Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

What's the difference with just using `<iframe ... />`?

See original GitHub issue

I’m trying to understand why anyone would use this library, where they can simply use a plain <iframe />.

What does this library do, apart from wrapping the iframe in a PureComponent, and limiting support to only the defined properties?

Issue Analytics

State:
Created 5 years ago
Reactions:4
Comments:9 (4 by maintainers)

Top GitHub Comments

5reactions

koenpuntcommented, Apr 14, 2019

I regarded the original question as rather hostile.

The only reason why you would think so is because apparently it is true; this library doesn’t provide any value over using a normal iframe.

But my question initially was out of interest, I was wondering if I maybe missed a special case.

Marketing this lib in that it has typescript types is not much added value either, given the fact that the html iframe tag already has types.

I think in general this library is misleading for newcomers to the ecosystem, and it could do better in actually explaining what this library does, and how people could go without.

3reactions

robbestadcommented, Apr 14, 2019

I’m sorry you don’t understand the point of this repo.i advise you to avoid it and use something else. I further advise you to spend your time searching out other libs you don’t like or agree with and ask them to provide alternatives.