Fullpage.js: Fullpage with Angular 6 Scroll Issue

[morganellis]

I use fullPage in two components that display the data for two separate pages (the 'home' and the 'about' pages), the rest of the pages on the site have normal scrolling and no navigation. When I click the browser's back or forward buttons going to either the home or about pages, I have issues with the scrolling. It loses its place and skips all over. I've tried adding anchors and tried only using fullPage in one component to be sure it's only initializing once (and tried the two together), but the problem still persists. I'm using Google Chrome and macOS ver 10.13.6, but the problem does remain on other browsers and operating systems. I'm just wondering if there's something simple that I'm missing or if there's some sort of trick with multi-page sites that I need to apply. Let me know, thanks!

Also, excellent work with this. You're great!

[alvarotrigo]

It loses its place and skips all over.

What do you mean by that? Any URL I can check?

Btw, I've started working on the Angular component for fullPage.js. Hope to have it ready in a month or two. (holidays in between)

UPDATE:

Here's the official component for Angular:
https://github.com/alvarotrigo/angular-fullpage

[vh13294]

It loses its place and skips all over.

What do you mean by that? Any URL I can check?

Btw, I've started working on the Angular component for fullPage.js. Hope to have it ready in a month or two. (holidays in between)

Is there a room for a contribution on your angular project?

[alvarotrigo]

@vh13294 sure! Please contact me and we can talk with more detail about it.

[vh13294]

I use fullPage in two components that display the data for two separate pages (the 'home' and the 'about' pages), the rest of the pages on the site have normal scrolling and no navigation. When I click the browser's back or forward buttons going to either the home or about pages, I have issues with the scrolling. It loses its place and skips all over. I've tried adding anchors and tried only using fullPage in one component to be sure it's only initializing once (and tried the two together), but the problem still persists. I'm using Google Chrome and macOS ver 10.13.6, but the problem does remain on other browsers and operating systems. I'm just wondering if there's something simple that I'm missing or if there's some sort of trick with multi-page sites that I need to apply. Let me know, thanks!

Also, excellent work with this. You're great!

You have to destroy the fullpage on ngOnDestroy:

`
fullpage_api = new fullpage(id, options);

ngOnDestroy() {
fullpage_api.destroy('all');
}
`

[alvarotrigo]

I release the official Angular component for fullPage.js a couple of weeks ago:
I would encourage you to make use of it from now on:
https://github.com/alvarotrigo/angular-fullpage