Why should child be aware of url?
See original GitHub issueIn 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 Results From Across the Web
Teach your Child to Identify Reliable Websites and Sources
Why Reliable Sources Matter. From an academic perspective, your child needs to be able to cite good quality sources in their work. They...
Read more >Children's Online Privacy Protection Rule: Not Just for Kids' Sites
The Children's Online Privacy Protection Rule seeks to put parents in control of what information commercial websites collect from their ...
Read more >Coronavirus Response | Keeping Children Safe Online
Kids should talk with a trusted adult so they understand online risks, only chat with people they know, ensure their online accounts are...
Read more >Keeping children safe online | NSPCC
We use cookies to give you the best possible experience on our website. Do you wish to accept cookies? This is OK. No,...
Read more >Home - Child Care Aware® of America
Child Care Aware of America is the nation's leading voice on child care issues. All families should have access to high-quality & affordable...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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?
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!