Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Target is in different component #79

Open
nhatzbulawan opened this issue May 5, 2018 · 9 comments
Open

Target is in different component #79

nhatzbulawan opened this issue May 5, 2018 · 9 comments

Comments

@nhatzbulawan
Copy link

Target destination is in different component


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ x] Feature request
[ ] Documentation issue or request
@harsimerkaur
Copy link

@nicky-lenaers is there are solution for this problem?
I have asked you same on stackoverflow as well. Kindly respond.
My source and destination component are different
Regards.

@harsimerkaur
Copy link

@nhatzbulawan Did you find any work around for this? Please respond. Thanks.

@nhatzbulawan
Copy link
Author

nhatzbulawan commented Jun 9, 2018

@harsimerkaur , I used the _scrollToService

@nicky-lenaers
Copy link
Owner

@nhatzbulawan Please provide an example on e.g. Stackblitz, so I can look into the problem. I need some more context for this.

Thanks!

@BenSegni
Copy link

BenSegni commented Feb 4, 2019

@nicky-lenaers Hi dude. I've stumbled across this issue too. I have a slider at the top of a one page website and the nav and main content is one component, website component and I have broken out the slider into it's own separate one. The values for the anchors are set within an api and are rendering in the browser, but scroll doesn't work. any ideas?

@robbertvancaem
Copy link
Collaborator

@BenSegni Could you please provide an example (e.g. Stackblitz or JSfiddle) of some sorts so we can follow along to see what you issue exactly is?

Thanks in advance! 🙏

@BenSegni
Copy link

BenSegni commented Feb 4, 2019

Hi @robbertvancaem - we have a workaround in place, but will share this stackblitz very shortly. Many thanks for the support. :)

@robbertvancaem
Copy link
Collaborator

@BenSegni Great that you found a workaround, would indeed be cool if you could still share a StackBlitz or something so we could investigate what could be improved.

@umar0645
Copy link

umar0645 commented Aug 3, 2021

I am facing the same issue, can you please share stackblitz?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants