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.

Why should child be aware of url?

See original GitHub issue

In my case I have a component which should be internationalised and distributed at language/country-code url paths.

Do I really need to change my components definitions for every single iframe?

Like:

de:

window.FooXComponent = xcomponent.create({
  tag: 'foo-x-component',
  url: 'http://www.example.org/de',

en:

window.FooXComponent = xcomponent.create({
  tag: 'foo-x-component',
  url: 'http://www.example.org/en',

Btw. I’m aware that I could move all i18n related props up to XComponent’s xprops. Tough I would not prefer to need to change that…

Issue Analytics

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

Top GitHub Comments

2reactions

AndyOGocommented, Sep 26, 2017

Sorry my question was not clear. I mean why does the child (the site which is rendered within the iframe itself) need to know about the url. Because I need to feed both the parent and the child with the created xcomponent.

I only see the point that the parent needs to know about the url because the parent will request that app, but why the child?

0reactions

bluepnumecommented, Oct 29, 2017

Going to close this for now unless anyone is having any residual issues. Seems like there are at least workarounds possible for the use-cases above. Thanks all!