Unable to capture scroll position in ngOnDestroy

[natcohen]

I'm submitting a ...

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
When checking the scroll position in ngOnDestroy(), it always returns 0

Expected/desired behavior
Should return the scroll position

Reproduction of the problem
http://plnkr.co/edit/OCdhEonzrkpRaT8iYB0i?p=preview

Check the console for the scroll position when clicking a button and when switching to the about menu

What is the expected behavior?
Return the scroll position

What is the motivation / use case for changing the behavior?
Would like to save the scroll position before the component is destroyed

Please tell us about your environment:

• Angular version:
  2.0.0-rc.5
• Browser:
  Chrome 52.0.2743.116 m
• Language:
  TypeScript

[zoechi]

Cross-link http://stackoverflow.com/questions/39091202/save-scroll-position-before-destroy

[IgorMinar]

when ngOnDestroy is called, the underlying element is no longer part of the document, so it's scroll position was reset by the browser.

a higher level event would be better to capture the scroll position. if you are using router then you can listen via CanDeactivate and capture the position there.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}